Actually, now is probably as good a time as any to change AC_MODULE_INIT to PIKE_MODULE_INIT or something similar, since the module API has changed anyway.
/ Per Hedbor ()
Previous text:
2003-01-27 12:27: Subject: Re: Module system and building modules (was Bz2)
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_*?
I suppose, but it might be a little bit late to change the name now. The macro has had this name since pike 0.6.
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?)
The whole point is that you don't have to "use this method" explicitly in any files; the files are exactly the same as when you compile in the main pike build tree.
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.
There were some others like "uninstall" mentioned though. Don't hesitate to think up more.
/ Marcus Comstedt (ACROSS) (Hail Ilpalazzo!)