From: Greg C. <gch...@sb...> - 2007-10-19 15:19:53
|
On 2007-10-19 13:53Z, John E./ TDM wrote: > > Greg Chicares <gchicares@...> writes: >> My advice would be to follow the instructions you quoted above: >> >> > other environments (such as UNIX or Unix-like, e.g. MSYS where you have >> > to use configure instead, see the section below) >> >> and build wx with MSYS. One advantage is that 'configure' >> will test for gcc and report if it's not found. Another is >> that you can use 'wx-config' (search the wx documentation) >> to pass the configuration you built wx with to your program >> that uses wx. Yet another is that you can customize wx by >> passing arguments to 'configure', which is the easiest >> approach to maintain--much easier than editing 'config.h' >> every time you want to build a new wx version. > > My advice would be *not* to do this. Building wxWidgets directly from the > command line is somewhat faster and quite a lot easier. How is it easier than 'configure && make'? > Finally, *editing > config.h is a very bad idea!* Oops, I meant 'setup.h', or 'setup0.h' (I can't remember which), but you're right: 'config.h' isn't the file to edit. |