-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Predef always fails on Windows with build-dir directive #32
Comments
I was unable to repo this with the latest Predef code (develop) on OSX. I'll try on Windows a bit later. But I suspect I wont be able to repo there either. As I rewrote the BBv2 way this works to only rely on compiling the check programs (i.e. doesn't run exes). Perhaps you could try using the current develop state to see if it resolves the issues for you? |
Finally got around to testing on Windows.. And sadly I get an error irrespective of the build-dir option. So still looking into it. |
OK.. And got to do some more testing on Windows, with all code updated.. And everything works for me on Windows. |
I updated my predef-test to the latest master and I still get the error. It still hinges on whether build-dir is specified or not:
|
…g/predef#32 gets fixed) Former-commit-id: ad7d037eaacb92a9b551aed713b5e6574837655e
Hi Rene,
I'm trying to use predef in my Boost.Build project but have run into a strange issue. The check programs like "predef_check_as_cpp.exe" are supposed to return 1 when the check is false, right? I created a test case showing some strange issues on Windows:
Jamroot.jam:
On Windows/MSVC-12, that's causing this:
You can see it's building as debug even if I build the rest of the project is building as release, and it's also passing the pdb to the check command. If I edit predef.jam to build as release, then it still fails, but this time it fails because the return code is 1. I don't understand that. The predef.jam code is pretty cryptic relative to my Boost.Build skills, so I'm not sure what's going on. If I get rid of the build-dir directive, it builds fine on Windows (although it's still debug). It builds fine either way on Linux.
The text was updated successfully, but these errors were encountered: