No defines using bjam on Windows with msvc
As I said in an earlier post, I'm trying to start using jam for our projects. I'm using Boost.Jam ver 3.1.4. When I build on Windows with TOOLS=msvc and use "bjam -d2", the command-line doesn't have any define flags on it. Several of our source files rely on "WIN32", e.g. to determine the platform. Has anyone seen this before? I feel like I'm overlooking something obvious, but I haven't been able to figure it out. Here's the beginning of the output from "bjam -d2": ***** ...found 156 targets... ...updating 11 targets... vc-Cc ..\..\libs\ETSopt\bin\libetsopt.lib\msvc\debug\runtime-link-dynamic\etsopt .obj "cl" /Zm800 -nologo -c /Z7 /Od /Ob0 /GX /GR /MDd -I"..\..\libs\ETSopt" -I"C:\PROGRA~1\MICROS~2\VC98\include" -Fo"..\..\libs\ETSopt\bin\libetsopt.lib\ msvc\debug\runtime-link-dynamic\etsopt.obj" "etsopt.c" etsopt.c ***** Thanks in advance, Phillip
Hi Phillip,
As I said in an earlier post, I'm trying to start using jam for our projects. I'm using Boost.Jam ver 3.1.4.
Please post Boost.Build questions to the Boost.Build mailing list.
When I build on Windows with TOOLS=msvc and use "bjam -d2", the command-line doesn't have any define flags on it.
Why do you think there should be any defines? Did you specify any?
Several of our source files rely on "WIN32", e.g. to determine the platform.
Then, you need to set this define.
Has anyone seen this before? I feel like I'm overlooking something obvious, but I haven't been able to figure it out.
Why do you think WIN32 should be automatically defined on Windows? All Windows compilers set _WIN32, which can be used in your headers. - Volodya
participants (2)
-
Phillip Seaver -
Vladimir Prus