From: Alex Besogonov (cyberax_at_[hidden])
Date: 2006-08-12 16:31:15
Rene Rivera wrote:
> Note... I'm close to having the wxWidgets support that builds wx done.
> Work obligations means I have have to get it done by Monday :-) That said...
How did you implement it? Using my wxWidgets.jam or by adding BBv2 files
to the wxWidgets' sources? Does your solution support library name
> OK, since I don't usually put down suggestions without providing
> alternatives, here's the alternative. We create a repository of non-core
> BB support. This might be similar CPAN, for example. The quickest, least
> effort first cut would be adding such packages to the Boost Valt
> <http://boost-consulting.com/vault/> in an appropriate directory, and
> adding detailed descriptions in the wiki if needed. Of course
> suggestions, i.e. solutions, on this are appreciated.
That's a good idea. I think Wiki and a project on SourceForge is the
right way for this. My favorite Wiki brand is
http://www.atlassian.com/software/confluence/ (it's free for OpenSource
I don't like Boost Vault, it's not easy to use and is known to have bugs.
> This does require some requirements, for consistency, on those packages.
> I'm trying to think of, and to follow, some of those requirements as I
> implement the wxWidgets compile support. The ones I have so far:
Good ideas. But we need one more thing from BBv2 to make it work - the
ability to use custom package search paths.
Currently I have to do something like this:
# Add 'tools' directory to module search path.
local x = [ modules.peek : BOOST_BUILD_PATH ] ;
modules.poke : BOOST_BUILD_PATH : $(TOP)/build/tools $(x) ;
We need something better and more user-friendly.
-- 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