My module, however, uses functions from another .c file in the same folder (functs.c), and I have included functs.h as well. When I load the module, I get 'undefined symbol' errors for the functions that are defined in functs.c. Is it because I should specify that file too in the makefile, somehow? Or should I absolutely avoid this and include the .c directly, kind of like how util.c is included?
I'm compiling this on Linux, by the way.
Edit: I tried adding this:
lvzhud_mods = lvzhud functs
and it seems to work... so I guess it's:
<dll or so file>_mods = <source files> ?
Dr Brain - Mon Jan 10, 2011 6:50 am Post subject:
Yeah, what you did is probably the simplest way to accomplish what you want.
Anonymous - Sun Jan 16, 2011 10:30 pm Post subject:
It is needed for you. When you want to add more functionality to your server you can install new custom modules. Differences in server versions often mean something will break in a module, compiling from source can help fix this.
Contents
[hide]
* 1 C modules
o 1.1 Using Makefile fragments
o 1.2 Using a custom Makefile
o 1.3 With Dev C++
+ 1.3.1 Step 1
+ 1.3.2 Step 2
thanks