CC = g++
SO_I = -c -fpic
SO_O = -shared -lm -o
%.o: %.c
$(CC) $(SO_I) $<
mod_olc.so: mod_olc.o cmd_olc.o cmd_olcarea.o cmd_olcroom.o cmd_olcobj.o cmd_olcnpc.o
$(CC) $(SO_O) mod_olc.so mod_olc.o cmd_olc.o cmd_olcarea.o cmd_olcroom.o cmd_olcobj.o cmd_olcnpc.o
CC = g++
SO_I = -c -fpic
SO_O = -shared -lm -o
H_FILES := $(wildcard ../core/*.h) $(wildcard ../classes/*.h)
%.o: %.c $(H_FILES)
$(CC) $(SO_I) $<
mod_olc.so: mod_olc.o cmd_olc.o cmd_olcarea.o cmd_olcroom.o cmd_olcobj.o cmd_olcnpc.o
$(CC) $(SO_O) mod_olc.so mod_olc.o cmd_olc.o cmd_olcarea.o cmd_olcroom.o cmd_olcobj.o cmd_olcnpc.o
So has anyone done any work relating to loading modules of code dynamically at run-time?
Ive been looking into this a little bit and came across information on dlopen, dlsym, and dlclose.
This appears to be the answer to my questions. I was wondering though if anyone has previously (and im sure some have)
have worked with loading code in this way.
Does it seem like a viable option?
Any disadvantages of this?
Thoughts, ideas, theories?
Is there any codebases out there that do this already?
Discuss