Compiling Boost 1.33.1 & getting success w/ XP!!
Hello all, for those who'd had problems like be getting boost to run after getting it to compile in w/ their App, here's what I did: 1. Got the absolute latest version of boost that was stable - 1.33.1 2. Followed the "Getting Started" Instructions better: a. in step 2 for XP, HAD to start a cmd tool b. HAD to run vcvarsall.bat (located @ C:\Program Files\Microsoft Visual Studio 8\VC\vcvarsall.bat on my computer) c. I'm using the toolset vc-8_0, therefore the need for step 2.b d. cd'ed to my Boost install directory - after getting the bjam executable for XP and copying it there 1st e. ran the following commands C:\Program Files\Microsoft Visual Studio 8\VC\vcvarsall.bat <return> bjam "-sTOOLS=vc-8_0" install 3. Took over 2 hrs to get the results in a NEW BOOST directory where only the "includes" and the "libs" were located. 4. Notice that I accepted the "default" libs that it generated. The Note on using the "-sBUILD" NEVER NEVER worked for me. The build processes kept trying to use .Net 2003 VC7 to compile with & of course couldn't find it! So boost never built correctly to begin with. Bummer! 5. Then I included the header directory in my .Net App: C:\Boost\include\boost-1_33_1 6. Thin I included the following "static" libraries in my .Net App: C:\Boost\lib\libboost_wserialization-vc80-mt-gd-1_33_1.lib C:\Boost\lib\libboost_date_time-vc80-mt-gd-1_33_1.lib C:\Boost\lib\libboost_filesystem-vc80-mt-gd-1_33_1.lib C:\Boost\lib\libboost_iostreams-vc80-mt-gd-1_33_1.lib C:\Boost\lib\libboost_prg_exec_monitor-vc80-mt-gd-1_33_1.lib C:\Boost\lib\libboost_program_options-vc80-mt-gd-1_33_1.lib C:\Boost\lib\libboost_regex-vc80-mt-gd-1_33_1.lib C:\Boost\lib\libboost_serialization-vc80-mt-gd-1_33_1.lib C:\Boost\lib\libboost_signals-vc80-mt-gd-1_33_1.lib C:\Boost\lib\libboost_test_exec_monitor-vc80-mt-gd-1_33_1.lib C:\Boost\lib\libboost_thread-vc80-mt-gd-1_33_1.lib C:\Boost\lib\libboost_unit_test_framework-vc80-mt-gd-1_33_1.lib C:\Boost\lib\libboost_wave-vc80-mt-gd-1_33_1.lib 7. I've NO clue what "gd" means but I sure hope it means the debug version. The docs DON'T explain this nor the -s either and I hope their updated soon to include the meaning of these nomenclatures. Well that's all & it works for me, FINALLY!!!!!!!!!!!! I'm so happy. Just wish I'd had feed back from the group on this issue but all's well that ends well. See y'all later!!! -- Sincerely, Allen Gene Allen Saucier, Jr Senior Software Engineer CAS, Inc 100 Quality Circle Huntsville, AL 35806 or PO Box 11190 Huntsville, AL 35814 (256) 922-6453 (w) "...As for I and my house, we shall follow the Lord" Joshua 24:15
Allen wrote:
7. I've NO clue what "gd" means but I sure hope it means the debug version. The docs DON'T explain this nor the -s either and I hope their updated soon to include the meaning of these nomenclatures.
"gd" means linking against the debug C/C++ runtime library and built debug code <http://boost.org/more/getting_started.html#Results>. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
Allen wrote: Hi Allen,
2. Followed the "Getting Started" Instructions better: There is a new and better "Getting Started" guide in cvs. Look for more/getting_started.html. 7. I've NO clue what "gd" means but I sure hope it means the debug version. The docs DON'T explain this nor the -s either and I hope their updated soon to include the meaning of these nomenclatures. They do. Search in the current Getting Started guide under Results / Runtime. There is a table that lists everything.
s - Static link to runtime. g - Debug runtime. y - Debug Python system. d - Debug enabled code. p - STLport runtime, instead of the vendor toolset runtime. n - STLport runtime using the "native" IO streams instead of the STLport IO streams. -- HTH dave
On 1/26/07, Allen <allen.saucier@cas-inc.com> wrote:
Hello all,
Hi Allen, There is an installer of boost for MS compilers. Didn't that work for you? http://www.boost-consulting.com/download.html
5. Then I included the header directory in my .Net App:
C:\Boost\include\boost-1_33_1 6. Thin I included the following "static" libraries in my .Net App:
you don't have to do this. Step 5 should be enough thanks to auto link (see http://tinyurl.com/2ged5u) -- Server Levent Yilmaz Mechanical Engineering @ PITT
On 1/26/07, Server Levent Yilmaz <leventyilmaz@gmail.com> wrote:
On 1/26/07, Allen <allen.saucier@cas-inc.com> wrote:
Hello all,
Hi Allen,
There is an installer of boost for MS compilers. Didn't that work for you? http://www.boost-consulting.com/download.html
5. Then I included the header directory in my .Net App:
C:\Boost\include\boost-1_33_1 6. Thin I included the following "static" libraries in my .Net App:
you don't have to do this. Step 5 should be enough thanks to auto link (see http://tinyurl.com/2ged5u)
correction, adding C:\Boost\lib to the additional library folders should be enough (this I thought what you said in step 5, sorry about that. :)
-- Server Levent Yilmaz Mechanical Engineering @ PITT
-- Server Levent Yilmaz Mechanical Engineering @ PITT
Allen wrote:
Hello all,
for those who'd had problems like be getting boost to run after getting it to compile in w/ their App, here's what I did:
[...]
For a very long time, I have been building boost using VS2003 or VS2005 project directly, not using bjam. What only need is adding some defines in boost\config\user.hpp and create several projects for library which have cpp, then build them in IDE or command line. Regards cg
participants (1)
-
Allen -
David Klein -
gchen -
Rene Rivera -
Server Levent Yilmaz