Boost logo

Boost-Build :

From: Vladimir Prus (ghost_at_[hidden])
Date: 2007-12-01 13:22:02

On Wednesday 21 November 2007 23:22:39 Mat Marcus wrote:
> I've made a number of changes to my universal-binary supporting
> darwin.jam patch (shipping with the Adobe Source Library) in order to
> address the concerns raised by Rene and others at
> :
> My current version supports invocations like:
> bjam architecture={combined,x86,power} link={shared,static}
> address-mode={64,32}
> That is, universal builds are now supported, along with 64 bit builds.
> I'd like to ask for the help from a few volunteers who'd be willing to
> test it out, before I submit my patch for consideration here. Anyone
> interested in helping me test it?
> One of the issues that remains pertains to folder naming. On the mac,
> if a build doesn't specify an -arch parameter, the architecture (and
> perhaps the address model) of the host machine is used. I'm not really
> comfortable with the same folder path meaning different things on
> different machines. So, I'd like to do something like the following in
> darwin.jam (in invented pseudo code)

Don't we have similar issue, in general? If you don't specify architecture,
explicitly, you get the default one.
> SWITCH(on result of /usr/bin/arch) { # host machine's architecture
> CASE(ppc) use <architecture>power/<address-mode>32 as the default
> CASE(i386) use <architecture>x86/<address-mode>32 as the default
> CASE(ppc64) use <architecture>power/<address-mode>64 as the default
> CASE(x86_64) use <architecture>x86/<address-mode>64 as the default
> DEFAULT error, unknown arch
> Can someone guide me in towards the right way to express this in bbv2?

I don't think we have a good solution now -- we probably need a general
way to compute feature defaults *AND* some way for user to decide if
default values of 'architecture' and other features are present in target path.

- Volodya

Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at