Anything that makes it easier and better is good by me. -John Labenski
On 2/14/07, Francesco Montorsi <[EMAIL PROTECTED]> wrote: > Hi all, > > now that bakefile 0.2.2 is out and that the wxpresets have been > greatly enhanced I'd like to make some BIG changes to wxCode bakefiles. > > I've been working on them today and yesterday and I've managed to get > many advantages: > > - extremely smaller Bakefiles.bkgen files > - _much_ cleaner bakefiles (less, more friendly code): you won't > even need to list your component's sources & headers anymore! > (Bakefile will automatically detect your component's sources & headers) > - painless setting of > => wx-style build directory to allow multi-builds with different > settings for WX_UNICODE/DEBUG/UNICODE > => wx-style "lib/[compiler]_lib" directory to allow multi-builds > => wx-style lib naming > - full support for "gnu" makefile format as alternative to the fat > "autoconf" format for Unix > > The new bakefile 0.2.2 also supports msvs2005 which is surely a Good > Thing (but see below) > > However all these changes have two drawbacks: > > 1) currently I've hit a bug in bakefile which makes it loop endlessly > when generating msvs2005prj and msvc6prj formats for the component samples > > 2) it requires modifications to all your component's build files: > > - Bakefiles.bkgen > - yourcomp.bkl > - configure.ac > > since the new bakefiles are incompatible with the previous ones. > > I've updated all the build systems of my components (changes not yet > committed) and I can say it requires about 30 minutes to do all the > changes to the build system. > > All in all, I'd say that as soon as the problem #1 will be fixed I'll > commit the new bakefiles (thus forcing everyone which wants to > regenerate its component's build system to do the upgrade)... what do > you say? > > Do you agree? > > I strongly think it's worth the effort also because I didn't describe in > details all the advantages you get - e.g. you now get a nice error > message like "The selected wx build does not exist" when you do "nmake > -fmakefile.vc WX_UNICODE=1" and you don't have any Unicode build of wx; > previously you only get a compiler error about an unreachable > "wx/wxprec.h"... > > Francesco > > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > wxCode-users mailing list > wxCode-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wxcode-users > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ wxCode-users mailing list wxCode-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxcode-users
