Thanks to that output (-a -odump.txt ), I found something interesting when doing testing. When you run the tests on the boost filesystem, it builds a static library at: bin\boost\libs\filesystem\build\libboost_filesystem.lib\mingw\debug\libboost_filesystem-mgw-d-1_32.lib It then deletes the library when the tests are over. If I break the build right after it builds this test library and then link to that library from my test program, the program executes without an exception! For some reason the library that the tests are building is working, and the libraries that are built using [ jam "-sTOOLS=mingw" stage ] are not working! I am very confused now. Any help will be greatly appreciated. - Dave "David Abrahams" <dave@boost-consulting.com> wrote in message news:ud5ret36u.fsf@boost-consulting.com...
"David Daeschler" <daveregs@rsaisp.com> writes:
Thank you for your reply. It looks like the tests all pass if I run them by using bjam and building them in their respective directories. However, if I compile the minimal.cpp file outside of the boost build environment (move the file somewhere else and build using make) the test fails.
I think I may be missing required compiler defines when I compile my test program, but I can't figure out what these may be.
As an example, I wrote a simple test program that currently fails under my configuration.
Try using
bjam -a -odump.txt ...whatever-you-normally-pass-to-bjam...
and then looking at dump.txt to see what options are being passed to the compiler. Then you can use them in your Makefile.
HTH, -- Dave Abrahams Boost Consulting www.boost-consulting.com
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost