|
Boost-Build : |
Subject: Re: [Boost-build] Changed behaviour of custom generators?
From: Roland Schwarz (roland.schwarz_at_[hidden])
Date: 2014-04-03 08:19:39
On 02.04.2014 17:10, Steven Watanabe wrote:
>
> Can you try running with -d+4 which should print
> out the string passed to CreateProcessA.
Ok, several things happened:
1)
The log entry changed to "Command string for CreateProcessA():
'-ftemplate-depth-128 ..."
which I know from earlier experience as indicating an inability of
boost-build to detect my compiler.
In my user-config.jam it is defined as:
using gcc
: 4.6.2
: "C:/subsys/win32/mingw-4.6.2/bin/g++.exe"
: <flavor>mingw32
<root>"C:/subsys/win32/mingw-4.6.2/"
<archiver>"C:/subsys/win32/mingw-4.6.2/bin/ar.exe"
<rc>"C:/subsys/win32/mingw-4.6.2/bin/windres.exe"
<cxxflags>-fno-strict-aliasing
<linkflags>-Wl,--allow-multiple-definition
;
And I request this compiler from the cmd line as:
b2 mytarget gcc-4.6.2-mingw32
which worked before, and still works for the 4.7.2 compiler which is
also in user-config.jam (altough it is the first compiler specified in
the file, the default compiler)
2)
A second observation is, that I am not able any-more to use
toolset-add-requirements within the user-config.jam to add requirements
(well indeed only a specific one) to my compilers
I.e.:
using gcc
: 4.7.2
: "C:/subsys/win64/mingw64-4.7.2/bin/g++.exe"
: <flavor>mingw64
<root>"C:/subsys/win64/mingw64-4.7.2/"
<archiver>"C:/subsys/win64/mingw64-4.7.2/bin/ar.exe"
<rc>"C:/subsys/win64/mingw64-4.7.2/bin/windres.exe"
;
toolset.add-requirements
<toolset-gcc:flavor>mingw64:<target-os>windows
<toolset-gcc:flavor>mingw64:<architecture>x86
<toolset-gcc:flavor>mingw64:<instruction-set>core2
<toolset-gcc:flavor>mingw64:<address-model>64
<toolset-gcc:flavor>mingw64:<threadapi>win32
;
Does not add architecture property (which my Jamroot depends on).
I hope you can help.
Thank you, Roland.
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