On Mon, Aug 25, 2014 at 01:45:58PM -0400, Andrew Piskorski wrote: > The stock Tcl win/README file says that they build with "Visual C++ > 6.0 and the TEA Makefile", but VC++ 6.0 is 32-bit only, so the > ActiveState folks must be doing something slightly different for > their 64-bit builds. Anybody know offhand what they really use or > where their 64-bit Windows build scripts are located?
Well, that question at least seems simple: The Tcl win/makefile.vc has lots of comments about turning on 64-bit support, etc. So presumably 64-bit ActiveTcl uses the stock Tcl build scripts on Windows. So I guess my fallback option is to use Tcl's makefile.vc as a guide in setting up a Naviserver Windows build environment from scratch. But do I actually need to do that? Maybe Naviserver already has some better support for Windows command-line builds and I just don't know how to use it correctly. If I do need to add something, of course I'm happy to contribute it back, so how would you folks like to see this stuff work? In general, what's the right way to do it? Is it actually feasible to have one set of makefiles support both Unix and Windows, or is the existence of Tcl's makefile.vc a big hint that that doesn't really work? Btw, the Fossil version history of Tcl's win/makefile.vc is here: http://core.tcl.tk/tcl/artifact/dafbf950b8cca6b71a1cc3b8fef858f32a6aeacc http://core.tcl.tk/tcl/finfo?name=win/makefile.vc -- Andrew Piskorski <a...@piskorski.com> ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ _______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
