On Sat, Apr 13, 2019 at 11:56 AM Andrey Semashev via Boost < boost@lists.boost.org> wrote:
As some of you may have noticed, there were some changes to B2 yesterday (4-12). As previously mentioned I merged the start of the B2 C++ engine port to the develop branch. That change included some "improvements" to
building of the B2 executable. One of those improvements may be causing people CI failures. The new build scripts for B2 now respect, and use,
On 4/13/19 4:27 PM, Rene Rivera via Boost wrote: the the
CXX and CXXFLAGS environment variables. As such it means that if you have those set for other reasons it may confuse the B2 build (i.e. bootstrap.sh/bat invocation) and fail that build. If that's the case you will need to clear those variables before invoking boostrap.sh/bat or build.sh/bat.
In Boost.WinAPI, with which I have reported the problem, I'm not setting CXX or CXXFLAGS. Regardless, I tried unsetting these variables before running bootstrap just in case they are set in the environment. It didn't help.
https://ci.appveyor.com/project/Lastique/winapi/builds/23824813/job/nv2g992b...
Well, that's interesting, and strange given that such a label does exist < https://github.com/boostorg/build/blob/develop/src/engine/config_toolset.bat...
.
-- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net