Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum wrote:
If you have a module.pmod.in and some C code, both the generated module.pmod and the .so file should be installed in the MODDIR subdirectory of the module directory. Maybe they aren't (the Parser module doesn't seem to use a module.pmod.in), but then that would be the bug to fix rather than add a new construct that does the same thing.
Ah, I see.. yes. Although there's no module.pmod.in when it's time for install. During make, it has been compiled into a module.pmod/... [all .pmod files from module.pmod.in/ ]
But the I guess it's the Parser that is bogus. Didn't see when it was used during install though. Have to make a closer look at this. Strange no one else seems to have noticed this though. Is my setup so uncommon?
Example of my setup:
Foo/ configure.in Makefile.in module.pmod.in foo.cmod
Foo/module.pmod.in/ module.pmod
make gives: module.pmod/module.pmod foo.c module.so install gives, at target module: ___Foo.so Foo.pmod/module.pmod desired after install: Foo.pmod/module.pmod Foo.pmod/___Foo.so
If module.pmod.in is a file, then install gives (correctly): Foo.pmod ___Foo.so (no .pmod dir)
The reason for having module.pmod in a dir named module.pmod.in is to be able to have more .pmod/.pike files installed with the module. Haven't found any other way, so I guess it's the supposed way of doing this... ?
//K