On Wed, Apr 04, 2007 at 07:38:11AM -0400, Reed Hedges wrote: > Well, automake works fine for me in general on MinGW whenever I've used > it there, but never tried it with Visual Studio or Cygwin. Of course > there's always the incompatible-versions problem with the autotools. > And maintaining a ton of visual C files sucks, I have to do that all the > time :)
Well automake essentially works, the real bastard on mingw and cygwin is libtool. Unfortunately you can't really use automake to build DLLs without libtool, at least not without a lot of hacking. My main beef with automake itself is that it doesn't have good mechanisms for applying rules across the whole project (so we end up with the "inplace" boilerplate at the bottom of every file) and recursive makefiles suck for parallel builds. It's not worth fighting with any more, and since we're going to be doing a lot of rewriting from scratch in s5, we might as well reboot the build system as well. > That's good. If we can keep those project/make files in the tree > without too much trouble then that would be an ok way to go. Let's also > keep the bakefile source in the tree and in the source release too, > especially if eventually we want vos to be buildable on all kinds of > server operating systems (and where admins want to just run "make" and > not have to install extra tools). Before settling on bakefile I still need to get an idea of the strengths and weaknesses of the Crystal Space build system (Perforce Jam), Boost.Build (Boost Jam) and Scons. Essentially bakefile is a meta-makefile more like automake but more abstract (and thus able to target a variety of underlying build tools), whereas Jam and Scons are full make replacements. I still need to determine what specific unique features Jam and Scons offer that might tip the decision in their favor. Incidentally, it's probably possible to write a bakefile backend to produce Jam and Scons files ;-) -- [ Peter Amstutz ][ [EMAIL PROTECTED] ][ [EMAIL PROTECTED] ] [Lead Programmer][Interreality Project][Virtual Reality for the Internet] [ VOS: Next Generation Internet Communication][ http://interreality.org ] [ http://interreality.org/~tetron ][ pgpkey: pgpkeys.mit.edu 18C21DF7 ]
signature.asc
Description: Digital signature
_______________________________________________ vos-d mailing list [email protected] http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
