boost/build
2
0
Fork 0
mirror of https://github.com/boostorg/build.git synced 2026-02-13 12:22:17 +00:00
Code Issues Projects Releases Wiki Activity

Make sure -fPIC is added when compiling objects declared with the 'obj' rule.

Browse Source 
[SVN r29369]
This commit is contained in:
Vladimir Prus
2005-06-02 09:24:24 +00:00
parent 2d41235e04
commit 2d83788eff
1 changed files with 18 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
src/tools/gcc.jam
View File

@@ -87,7 +87,24 @@ flags gcc.compile OPTIONS <profiling>on : -pg ;
# inside 'init'.
if [ os.name ] != CYGWIN && [ os.name ] != NT
{
flags gcc.compile OPTIONS <link>shared/<main-target-type>LIB : -fPIC ;
# This logic will add -fPIC for all compilations:
#
# lib a : a.cpp b ;
# obj b : b.cpp ;
# exe c : c.cpp a d ;
# obj d : d.cpp ;
#
# This all is fine, except that 'd' will be compiled with
# -fPIC even though it's not needed, as 'd' is used only in
# exe. However, it's hard to detect where a target is going to
# be used. Alternative, we can set -fPIC only when main target type
# is LIB but than 'b' will be compiled without -fPIC. In x86-64 that
# will lead to link errors. So, compile everything with -fPIC.
#
# Yet another alternative would be to create propagated <sharedable>
# feature, and set it when building shared libraries, but that's hard
# to implement and will increate target path length even more.
flags gcc.compile OPTIONS <link>shared : -fPIC ;
}
if [ os.name ] != NT
{