Ideally, it would be good to have a method that handles these variations on the standard pike-distribution-module theme.
I think there already are provisions for this. Marcus?
Um, I'm not sure what you're thinking about now. Modules can be compiled inside or outside of the build tree, but any limitations of dynamic_module_makefile and common_module_makefile will of course apply to both cases.
/ Marcus Comstedt (ACROSS) (Hail Ilpalazzo!)
Previous text:
2003-08-19 18:30: Subject: module build/install procedure
- It appears that as far as pike is concerned, C modules can reside
anywhere in the module tree, as long as they're a .so file.
Correct.
- The dynamic module makefile, however, appears to have no provision for
making modules that don't live at the root of the namespace
Not true in Pike 7.5. Use makefile variable MODDIR to specify the subdirectory.
- Similarly, the dynamic module makefile doesn't seem to want to deal
with modules that either a) have no compiled module component, or b) have more than 1 pike file component, which is assumed to be called module.pmod.in and ends up as ModuleName.pmod, derived from the directory name that is being built in.
Correct. This is probably rather easy to fix in modules/common_module_makefile.in .
Ideally, it would be good to have a method that handles these variations on the standard pike-distribution-module theme.
I think there already are provisions for this. Marcus?
- We should have a way to insert information into the modref when a new
module is installed. This way, if I add a new module, the inline documentation is integrated with the existing modref. Now, I'm not very knowledgable on how this works, but I'm guessing that it would probably involve both installing documentation as part of the build procedure, along with some of the source [xml] files that would be needed to rebuild the documentation after inserting the new material.
This is probably solved easiest by installing the full intermediate XML file autodoc.xml, and joining the new XML files to it. The autodoc tools are already installed, however the structure files currently aren't.
- In order to do an integrated module install/remove feature, we probably
need a "receipts" store to keep track of what files belong to with modules, so we can be sure that we delete all of a module, or don't overwrite portions another module accidentally. Part of this could probably be accomplished by making a wrapper to mkdir,install,etc that added or removed entries from a contents file ala the solaris package manager.
This sounds like stuff to put in Tools.Standalone.module.
/ Henrik Grubbström (Lysator)