Find out which build options were used
Hello, is there somewhere in the boost directory a log file or something else where I can find out how the boost libraries where build? The problem is the following, a college of mine build an old version of boost. The college is not longer in our company and I want to update the library to 1.55.0, but I don't know the preprocessor variables and/or options he used. Any help would be great. Thanks so much
AMDG On 04/04/2014 11:52 AM, NoRulez wrote:
is there somewhere in the boost directory a log file or something else where I can find out how the boost libraries where build?
The problem is the following, a college of mine build an old version of boost. The college is not longer in our company and I want to update the library to 1.55.0, but I don't know the preprocessor variables and/or options he used.
This information is not recorded. If you're using msvc, you can get most of the raw options from the .rsp file in the build directory, but there's nothing like this for most toolsets. In Christ, Steven Watanabe
Ok, thanks but I need it for Mac OS X
Am 04.04.2014 um 21:38 schrieb Steven Watanabe
: AMDG
On 04/04/2014 11:52 AM, NoRulez wrote: is there somewhere in the boost directory a log file or something else where I can find out how the boost libraries where build?
The problem is the following, a college of mine build an old version of boost. The college is not longer in our company and I want to update the library to 1.55.0, but I don't know the preprocessor variables and/or options he used.
This information is not recorded. If you're using msvc, you can get most of the raw options from the .rsp file in the build directory, but there's nothing like this for most toolsets.
In Christ, Steven Watanabe
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
AMDG On 04/04/2014 02:08 PM, NoRulez wrote:
Am 04.04.2014 um 21:38 schrieb Steven Watanabe
: On 04/04/2014 11:52 AM, NoRulez wrote: is there somewhere in the boost directory a log file or something else where I can find out how the boost libraries where build?
The problem is the following, a college of mine build an old version of boost. The college is not longer in our company and I want to update the library to 1.55.0, but I don't know the preprocessor variables and/or options he used.
This information is not recorded. If you're using msvc, you can get most of the raw options from the .rsp file in the build directory, but there's nothing like this for most toolsets.
Ok, thanks but I need it for Mac OS X
Well, there's no way to get that information from Boost.Build. Sorry. The build of Boost needs to be compatible with your project. If you are using any flags that break ABI compatibility (such as -D_GLIBCXX_DEBUG), then you need to build Boost with those flags. If you're not doing anything special, the default build settings should work. (Of course, if you're only using header-only libraries, then there's no need to build anything.) In Christ, Steven Watanabe
Ok, I will give it a try. Thank you very much
Am 04.04.2014 um 23:30 schrieb Steven Watanabe
: AMDG
On 04/04/2014 02:08 PM, NoRulez wrote:
Am 04.04.2014 um 21:38 schrieb Steven Watanabe
: On 04/04/2014 11:52 AM, NoRulez wrote: is there somewhere in the boost directory a log file or something else where I can find out how the boost libraries where build?
The problem is the following, a college of mine build an old version of boost. The college is not longer in our company and I want to update the library to 1.55.0, but I don't know the preprocessor variables and/or options he used.
This information is not recorded. If you're using msvc, you can get most of the raw options from the .rsp file in the build directory, but there's nothing like this for most toolsets.
Ok, thanks but I need it for Mac OS X
Well, there's no way to get that information from Boost.Build. Sorry.
The build of Boost needs to be compatible with your project. If you are using any flags that break ABI compatibility (such as -D_GLIBCXX_DEBUG), then you need to build Boost with those flags. If you're not doing anything special, the default build settings should work. (Of course, if you're only using header-only libraries, then there's no need to build anything.)
In Christ, Steven Watanabe
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
participants (2)
-
NoRulez
-
Steven Watanabe