Am 17.09.14 23:19, schrieb Andrew Piskorski: > The Naviserver makefiles often definite a LIB variable, e.g.: > > LIB = nsthread What is the exact problem you see: is it the case, when LIB is set in a Makefile (as cited), or is the problem, when it is *not* set. In the latter case, "make" picks up the value of the environment variable and the logic in Makefile.module fails.
If the latter is the problem, would it be an option to set in the makefiles LIB to empty and to change the logic from "if LIB exists" to "exists and noempty" in Makefile.module? Would this help for the windows nmake build? > What's the best fix for this variable collision problem? Would it be > clearest to just rename all of Naviserver's uses of LIB to something > else? (DLL? LIB_NAME? MYLIB?) Makefile.module defines # LIB Root name of dynamic library (without lib prefix or extension) # LIBOBJS List of library object files (required with LIB) # LIBHDRS List of public header files to install (required with module LIB) If we have to change the name, this involves potentially all modules, making mixing versions of modules and naviserver impossible (which is probably not a good idea either, and not so bad, since we have the matching modules also in the sourceforge tar files). Note that LIB is not not only used for dynamic builds, but as well for static builds, so DLL is misleading. if we have to go this way, i would prefer LIBRARY, also LIBNAME is an option, but MOD has a similar purpose and is not called MODNAME (but is also not called MODULE). > Note that I'm currently running into this because the example Windows > nmake files Ibrahim Tannir of Archiware sent me mostly replace only > include/Makefile.module, and re-use Naviserver's stock per-module > makefiles. At first glance that seems reasonable to me, as most of > the per-module makefiles are very simple, and should presumably work > correctly in both Gnu make and Window nmake. replacing the Makefile.module for windows is as well also an option, and is a more local change and gives finally more freedom for windows adjustments... -g ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
