As I found with the original version of Minisec and the MySQL modules, inter-module dependency is a *really* bad idea.
Why isn't TinyXml++ packaged? If it's that small, then just putting it in your risk tree would be ok. If eventually the core of tpserver-cpp would provide it, then I would build it as a library like libltdl. That is actually an option now. Instead of building it as a module, build it as a full ltlibrary called libtptinyxml. Then you can either statically link your module against the library, or dynamically. Hope this helps. Later Lee On Sat, 12 Jul 2008, Ryan Neufeld wrote: > So in the process of including TinyXML++ in my ruleset I've run into a > little dilema. Do dump the 8 or so source files into my ruleset > directory, or more formally create a module called ticpp (or anything, > really) and then use that module from within the ruleset? > > It was my impression that dumping the source files was a bad idea, so > up until now I have been attempting to create a module/lib for > "ticpp." I have no problem compiling and installing the lib, and it > appears as if a proper directory is being created to house it, but I > am unable to load the lib at runtime. Here are the bits and pieces... <snip> > > I'm obviously doing some things wrong here, and I would appreciate > any help in getting things going. I'll commit my WIP branch to my > Risk branch and make sure things still run correctly without map > import, incase anyone would like to take a look at my source. > > Please let me know if you need additional info. Thanks, > > Ryan 'jphr' Neufeld
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ tp-devel mailing list [email protected] http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel
