Plugin support

[ray73864]

It's kinda rough.

Needs a directory in the rootdir called 'plugins', all works though.

Also needs 3 flags added to root/Makefile:
2 in LDFLAGS:
-Wl,--unresolved-symbols=ignore-in-object-files
-rdynamic

1 in CLIBS:
-ldl

An example test plugin:

#include <stdio.h>
#include <stdbool.h>
#include "config.h"
#include "conf.h"
#include "dbdefs.h"
#include "strutil.h"
#include "parse.h"
#include "function.h"
#include "notify.h"
#include "log.h"
#include "game.h"

void test_notify() {
  dbref player;
  player = 1;
  notify_format(player, "Hi %d!!", player);
}

FUNCTION(local_test_notify)
{
  test_notify();
  return;
}

int plugin_init(void) {
  function_add("TESTNOTIFY", local_test_notify, 0, 0, FN_REG);
//  do_rawlog(LT_ERR, "Hi");
  return 1;
}

Test plugin is compiled by doing

gcc -shared -fPIC -I.. -I../hdrs -o test.so test.c

in the plugins directory.

At that point you can either start up your game or @shutdown/reboot your game.

Plugin requires a 'plugin_init()' function, and can optionally have a 'plugin_timer()' function if you need to run something in your plugin every second.

[HarryCordewener]

Why not add the flags to the Makefile for the submission?

[ray73864]

There, the configure script does the flags for Makefile now.

[ray73864]

Now allocates memory for the array on a needs basis as it finds more plugins to load instead of defaulting the array size to only allowing 100 max

[talvo]

I haven't really looked at the code yet, but I'd like to see a more robust interface for this, particularly with some kind of versioning for future-proofing so more features can be added and we can tell what level of support any given plugin provides. It would also be nice if plugins had a method to report their own name, plugin version, interface version, etc, that could be displayed somewhere (probably in something like @config/plugins or the like). Linked list of a struct to store that info rather than a calloced array may be an easier approach for storing that.

[ray73864]

Have switched to using a doubly linked list instead of the array.

Will look at a better way of handling the plugins that support certain features, especially the timer feature, it's not really a problem when you only have 1 or 2 plugins, but if you have lots of plugins, it would be handy if the penn local_timer() knew ahead of time exactly which plugins to target instead of going through the entire linked list each time.

[ray73864]

Will look at the version support later on, for now the basics :)

[ray73864]

The latest PR should never have happened :)

I was trying to figure out Githubs changes since I last actively used it for doing commits, etc...

[ray73864]

Closing for now. I dislike the fact that the PR keeps getting updated everytime I push a change.