From: Alex Besogonov (cyberax_at_[hidden])
Date: 2006-07-29 16:35:02
Rene Rivera wrote:
>> 2. Define WX_HOME environment variable on Windows (POSIX systems need
>> wx-config script to be present somewhere in PATH).
> First off, env vars are not a good thing. We are explicitly avoiding
> such things in BBv2.
It's possible to specify wxWidgets' home as a parameter:
import wxWidgets : c:/tools/wxWidgets ;
>> There is still some work to do:
> Second, general question... Does this only work for prebuilt wx libs? Or
> will it also build wx itself from the sources?
No. wxWidgets uses its own build system (bakefiles) - it is possible to
add BJam project generation to Bakery, but it will require some work and
knowledge of both build systems.
Usually, custom wxWidgets builds are required for vendor-specific
library names, so I added support for it to my module. You can use it
One can also specify graphics toolkit: GTK, Win32, X Windows
(<wx-toolkit>), Unicode build (<wx-unicode>), usage of WX universal
library (<wx-universal>), WX linkage (<wx-link>) and version number.
> I'm asking because my use case is the latter. And I was about to start
> writing such a BBv2 extension.
That's a lot of work.
-- With respect, Alex Besogonov (cyberax_at_[hidden])
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk