How is build.env supposed to work ...

[Peter Danecek]

On Nov 19, 2013, at 18:38 , Ryan Schmidt <ryandesign at macports.org> wrote:

> On Nov 19, 2013, at 10:49, Peter Danecek wrote:
> 
>> So am I right if I assume that some of the environment variables are reset to a different value, AFTER I try to set them and before build?
> 
> There are a small number of variables that MacPorts puts into the environment of each phase, regardless of the value of $phase.env, including CC_PRINT_OPTIONS, CC_PRINT_OPTIONS_FILE, CPATH, LIBRARY_PATH, and MACOSX_DEPLOYMENT_TARGET. The first two cannot be changed; the others can be changed by setting the options compiler.cpath, compiler.library_path and macosx_deployment_target, respectively.
> 

Thanks Josh & Ryan!

This were the details I was looking for. I have not found it mentioned in the Guide. This is not there, right? Shouldn't we add it?
~petr


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1762 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macports-dev/attachments/20131119/0d09ae0e/attachment.p7s>