On Sunday, January 26, 2003, at 08:00 PM, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum wrote:
Pike modules have autoconf scripts, yes. They should contain AC_MODULE_INIT, and any specific tests that the module code itself needs.
Which pike to compile for is determined by which pike you use to run `pike -x module' through.
Ahh, I see, though isn't there a potential for name clash with AC_*? It wasn't at all clear to me that this system even existed. How exactly is it supposed to fit together (ie does someone have some files that use this method?)
dynamic_module_makefile defines such a set. But maybe it should be larger than what it is today.
I did have a quick look at that, and it seems to have the basics down (build, install, test, etc) that I'd consider critical.
You don't have to worry about smartlink and precompile; smartlink is handled totally transparently, and for precompiled stuff you only need to make a dependency on the cmod file and dynamic_module_makefile will handle the rest.
Thanks for the clarification... it seems to be more of a head start than I imagined.
Bill