Boost logo

Boost-Build :

From: Mat Marcus (mat-lists_at_[hidden])
Date: 2005-06-21 00:45:51

Hash: SHA1

- --On Saturday, June 18, 2005 10:30 AM -0400 David Abrahams
<dave_at_[hidden]> wrote:

> Mat Marcus <mat-lists_at_[hidden]> writes:


>> <
>> ary/universal_binary_intro/chapter_1_section_1.html>
>> <
>> seNotes/index.html#//apple_ref/doc/uid/TP40002069>
>> These may give you some idea about "universal" artifacts and gcc 4.0
>> changes. In addition to the various combinations of -arch settings,
>> there are two other build variables of which I am aware. First, the
>> toolchain's behavior is affected by the environment variable,
>> MACOSX_DEPLOYMENT_TARGET, which typically is set somewhere between
>> 10.1 and 10.4 at the moment, and determines the oldest OS version
>> upon which the targeted artifacts will run.
>> *** Question 2
>> Is there an existing bbv2 paradigm into which we can shoehorn this
>> notion?
> Sorry, what's "this" referring to?

The value of the environment variable MACOSX_DEPLOYMENT_TARGET (typically
10.2, 10.3 or 10.4u if I understand correctly) determines the oldest
version of the OS on which the built artifacts can be used. For some reason
Apple chose not to make it an environment variable instead of a command
line compiler flag. I am asking for the best way to expose this build
parameter in the darwin toolset. For example, could bbv2 set/export the
environment variable according to the value of a feature, say
<deployment_target>, so that the it would be visible to the generated
compilation commands? Or maybe there is a better approach.


Version: PGP Desktop 9.0.1 (Build 2185)



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