From: Vladimir Prus (ghost_at_[hidden])
Date: 2002-12-11 03:56:04
David Abrahams wrote:
>> V2 is almost capable of working on my own project, except that BB16
>> get in my way.
>> I hope Dave will look at BB16, and then look at toolset flags (BB4).
> Hmm, the database appears to be unavailable to me. I get a 404.
> I don't know what the numbers mean from memory ;-/
One of two memory modules has failed yesterday, so the server was
almost down. It should be working now.
>> Speaking about my plans, there is some polishing:
>> 1. I'd like to hardcode dll paths in debug builds. Should be easy, except
>> for learning the right way to do it.
> I don't think we want to do that unconditionally. Lots of people like
> to install debug builds, for whatever reason. I also think we won't
> be able to escape the need to set up the environment properly for
> testing from withing Boost.Build -- e.g. people might want to test
> release builds that way, or they might need PYTHONPATH set, or...
> So I'm not completely sure it's worth investing in this.
I was unclear. We certainly need <dll-path>. After it's there,
a *new" feature <hadrcode-dll-paths> can be added. It will be simple,
and won't be on by default. Note that you can't achieve this effect with
dll-path alone: you'd need to list full paths to all libraries when linking
and only Boost.Build knows those paths.
>> 2. Allow single build directory at project root (BB7)
> Or anywhere else, I hope!
>> 3. BB14 -- toolset specific suffixes. This should allow to use "so"
>> on NT/gcc and "dll" on NT/borland, at the same time.
> I think we clarified that NT always requires "dll".
Did we? Anyway, "lib"/"a" difference is still there.
>> Does the job division above look OK?
> Can't tell until I can see the server.
Hope you'll be able to look now.
>> BB6 is toolset implementation.
>> There's gcc support and preliminary borland support. Unfortunately, I
>> don't understand some parts of current gcc-tools.jam, so
>> can't do anything about it. We'd probably want MSVC support too, ASAP,
>> but I have no clue about import libraries, PCH, PDB, and it fact, don't
>> have that compiler.
>> Dave, Rene, I really hope for your assistance here.
> I'd be pleased to help. Right now I'm just trying to get started
> writing a CUJ article on Boost.Python. I should be able to mix in
> some BBv2 work.
-- Regards, Vladimir
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