Naviserver's include/nsversion.h is auto-generated from nsversion.h.in when running configure (or autoconf). How is that supposed to work when building on Windows? I've avoided the problem for now by simply running configure on Linux and using the generated file, which obviously isn't the right approach.
Is the idea to actually run configure on Windows, in Cygwin or something? So far I have haven't needed it for anything else. Also, what is the point of generating nsversion.h like this anyway? All that file seems to do is define constants like NS_MAJOR_VERSION, so by using autoconf/configure, we set their canonical values in configure.ac rather than directly in nsversion.h. Why is that a win? -- Andrew Piskorski <a...@piskorski.com> ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
