
Hi, I just built boost 1.36 for the mac and all the library names have xgcc40 inserted in the middle, such as libboost_iostreams-xgcc40-mt-1_36.dylib. It breaks my makefiles that contain the option " -lboost_iostreams". Is there a reason for the xgcc40 in this version and not the others, and is there a way to instruct bjam not to include it in the filename. Thank, s

AMDG Alain Leblanc wrote:
I just built boost 1.36 for the mac and all the library names have xgcc40 inserted in the middle, such as libboost_iostreams-xgcc40-mt-1_36.dylib. It breaks my makefiles that contain the option " -lboost_iostreams". Is there a reason for the xgcc40 in this version and not the others, and is there a way to instruct bjam not to include it in the filename.
Pass --layout=system to bjam to prevent the library names from being mangled with the compiler/options/version. In Christ, Steven Watanabe

Thanks. bjam --help describes it well. Probably a case where RTFM
would have been an appropriate answer.
a
2008/10/28 Steven Watanabe
AMDG
Alain Leblanc wrote:
I just built boost 1.36 for the mac and all the library names have xgcc40 inserted in the middle, such as libboost_iostreams-xgcc40-mt-1_36.dylib. It breaks my makefiles that contain the option " -lboost_iostreams". Is there a reason for the xgcc40 in this version and not the others, and is there a way to instruct bjam not to include it in the filename.
Pass --layout=system to bjam to prevent the library names from being mangled with the compiler/options/version.
In Christ, Steven Watanabe
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

On Tue, Oct 28, 2008 at 1:10 PM, Alain Leblanc
Thanks. bjam --help describes it well. Probably a case where RTFM would have been an appropriate answer.
a
2008/10/28 Steven Watanabe
: AMDG
Alain Leblanc wrote:
I just built boost 1.36 for the mac and all the library names have xgcc40 inserted in the middle, such as libboost_iostreams-xgcc40-mt-1_36.dylib. It breaks my makefiles that contain the option " -lboost_iostreams". Is there a reason for the xgcc40 in this version and not the others, and is there a way to instruct bjam not to include it in the filename.
Pass --layout=system to bjam to prevent the library names from being mangled with the compiler/options/version.
In Christ, Steven Watanabe
I'm responding to this topic to ask about how to make the LIB files not prefix with "lib". For example, right now I'm running the following command: bjam --toolset=msvc --build-type=complete --layout=system debug stage An example of how a library is output is: libboost_filesystem-mt-gd.lib I would like the libs to look like: boost_filesystem-mt-gd.lib Any idea how I can do this? Also, I need to figure out how to make the boost build process dynamically link against the standard C++ libraries, as right now it is statically linking against them.

On Sun, Nov 16, 2008 at 11:56 AM, Robert Dailey
On Tue, Oct 28, 2008 at 1:10 PM, Alain Leblanc
wrote: Thanks. bjam --help describes it well. Probably a case where RTFM would have been an appropriate answer.
a
2008/10/28 Steven Watanabe
: AMDG
Alain Leblanc wrote:
I just built boost 1.36 for the mac and all the library names have xgcc40 inserted in the middle, such as libboost_iostreams-xgcc40-mt-1_36.dylib. It breaks my makefiles that contain the option " -lboost_iostreams". Is there a reason for the xgcc40 in this version and not the others, and is there a way to instruct bjam not to include it in the filename.
Pass --layout=system to bjam to prevent the library names from being mangled with the compiler/options/version.
In Christ, Steven Watanabe
I'm responding to this topic to ask about how to make the LIB files not prefix with "lib". For example, right now I'm running the following command:
bjam --toolset=msvc --build-type=complete --layout=system debug stage
An example of how a library is output is:
libboost_filesystem-mt-gd.lib
I would like the libs to look like:
boost_filesystem-mt-gd.lib
Any idea how I can do this? Also, I need to figure out how to make the boost build process dynamically link against the standard C++ libraries, as right now it is statically linking against them.
I just realized what is going on. It's building both the dynamic and static versions of boost. Not sure how to tell it to build just the dynamic versions. The static libraries have the "lib" prefix it seems.

Robert Dailey wrote:
On Sun, Nov 16, 2008 at 11:56 AM, Robert Dailey
wrote: On Tue, Oct 28, 2008 at 1:10 PM, Alain Leblanc
wrote: Thanks. bjam --help describes it well. Probably a case where RTFM would have been an appropriate answer.
a
2008/10/28 Steven Watanabe
: AMDG
Alain Leblanc wrote:
I just built boost 1.36 for the mac and all the library names have xgcc40 inserted in the middle, such as libboost_iostreams-xgcc40-mt-1_36.dylib. It breaks my makefiles that contain the option " -lboost_iostreams". Is there a reason for the xgcc40 in this version and not the others, and is there a way to instruct bjam not to include it in the filename.
Pass --layout=system to bjam to prevent the library names from being mangled with the compiler/options/version.
In Christ, Steven Watanabe
I'm responding to this topic to ask about how to make the LIB files not prefix with "lib". For example, right now I'm running the following command:
bjam --toolset=msvc --build-type=complete --layout=system debug stage
An example of how a library is output is:
libboost_filesystem-mt-gd.lib
I would like the libs to look like:
boost_filesystem-mt-gd.lib
Any idea how I can do this? Also, I need to figure out how to make the boost build process dynamically link against the standard C++ libraries, as right now it is statically linking against them.
I just realized what is going on. It's building both the dynamic and static versions of boost. Not sure how to tell it to build just the dynamic versions.
See: http://www.boost.org/boost-build2/doc/html/bbv2/advanced/invocation.html - Volodya
participants (4)
-
Alain Leblanc
-
Robert Dailey
-
Steven Watanabe
-
Vladimir Prus