|
Boost-Build : |
Subject: Re: [Boost-build] User environment ignored during testing
From: Michael Jackson (mike.jackson_at_[hidden])
Date: 2008-12-15 13:56:40
Right, On OS X with Intel version 10 at least you can use the static
versions of the _intel_ libraries but still use the OS X runtime
libraries (which is all Apple supports any ways).
the flag is -static-intel.
From the intel C++ Version 10 user guide:
static-intel
Causes Intel-provided libraries to be linked in statically.
IDE Equivalent
Windows: None
Linux: None
Mac OS X: Libraries > Intel Runtime Libraries
Architectures
IA-32 architecture, Intel® 64 architecture, IA-64 architecture
Syntax
Linux and Mac OS X:
-static-intel
Windows:
None
Arguments
None
Default
OFF
Intel libraries are linked in statically, with the exception of
libguide. Note that when this option is specified, libguide is also
linked in statically.
Description
This option causes Intel-provided libraries to be linked in
statically. It is the opposite of -shared-intel.
Alternate Options
Linux and Mac OS X: i-static (this is a deprecated option)
Windows: None
See Also
shared-intel compiler option
--- Mike Jackson www.bluequartz.net On Dec 15, 2008, at 1:31 PM, K. Noel Belcourt wrote: > > On Dec 15, 2008, at 11:25 AM, Michael Jackson wrote: > >> If i remember correctly if you use --static-intel flag (or something >> like that) then icc will statically link its own libraries into your >> code instead of using the dylibs. That would get around the >> environment issues. > > True, but I'm not building with runtime-link=static, I'm building > with runtime-link=shared. > > -- Noel > > > _______________________________________________ > Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
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