I'm speaking on Boost.Thread this year at BoostCon'08.
Here is the announcement from the Boost mailing list:
Reminder: early registration for BoostCon'08 closes Monday, April 7.
It's still not too late to avoid the late registration fee for what may
be the finest C++ event of 2008.
For the 2nd annual Boost C++ libraries conference, we've put together a
fantastic program crowned by a keynote address from Bjarne Stroustrup.
In addition to existing Boost libraries, we're covering technology of
interest to any C++ developer trying to stay on the cutting edge,
including hands-on sessions with features from the upcoming 2nd version
of the C++ standard. This year we've also added a collection of short
"author's corner" sessions for those of you who want an inside
perspective on how advanced libraries are developed. See
http://www.boostcon.com/program for details.
BoostCon 2008 will be hosted at Aspen Center for Physics, one of the
most beautiful meeting sites in the world, and a great venue for
collaboration and discovery. The combination of a relaxed pace and
intense inquiry made BoostCon'07 an event to remember, and we expect no
less for this year. Please visit http://www.boostcon.com/registration
to register.
Thanks!
-- The BoostCon Planning Committee
David Abrahams
Beman Dawes
Jeff Garland
Joel de Guzman
Eric Niebler
Sean Parent
Jeremy Siek
Matthias Troyer
Showing posts with label Boost. Show all posts
Showing posts with label Boost. Show all posts
Wednesday, April 02, 2008
Monday, March 31, 2008
Building Boost 1.35.0
Seems I always have troubles building Boost.
To start I followed the big 'Get Boost' button on the right side of boost.org; thinking, 'That sure is obvious'. That link takes you to a download page with boost version 1.35.0 right at the top. It shows the new libs with 'Detail' and 'Download'. I took a few seconds to read the new libs section and clicked on download. This took me to sourceforge.net where they have the source code only release. Well, I knew that Boost Consulting has maintained an installer for Windows assuming you are using boost with Visual Studio. So I jumped over to their boost installer site, only to find that they don't have one yet for 1.35.0.
No problem, I'll just go back and grab the source code from sourceforge.net and follow the instructions in the getting started document. I kicked off the download and started looking for the getting started document. After a while, I figure I must be crazy, because I can't find it. I finally do a google search in order to find it. Still thinking I must have just missed it, I went back and followed every link on the right of the the main boost site. It is not under 'Introduction' or any other of the sections. I finally did locate it, it is on the main page on the left under 'GETTING STARTED'. Funny how you can look right past something like that.
So now I figure all I have to do is follow the getting started guide to build boost.
Step 1. Get Boost. I already did that. My download had already completed from sourceforge.net. I unziped it (actually un-7zed it) to c:\boost\boost_1_35_0\.
Step 2. Explain Boost Distribution. Ok, nothing new here.
Step 3. Header only libs. Right, header only libs are nice. Just compile and go. However, Boost.Thread among others need to be compiled.
Step 4. Build with a header only lib. Been there done that many times. There are sub-steps for building with Visual Studio. I always use MPC, so this is not useful to me. I plan to create a separate post or two about building boost applications with MPC. When you see how easy it is to use MPC with Boost, I doubt that you will use anything else.
Step 5. Building Boost libraries. Alright, here we go.
Step 5.1. Install Boost libraries. Yeah, thats what I wanted to do to start with. However, Boost Consulting has not yet put out an installer for 1.35.0.
Step 5.2. Build from source.
Step 5.2.1. Get bjam. I put the executable in c:\boost\boost_1_35_0\.
Step 5.2.2. Identify toolset. I want: msvc.
Step 5.2.3. Select a build directory. It says this is not necessary.
Step 5.2.4. Invoke bjam. This is where I got in trouble. I tried various combinations of commands/arguments to bjam. I must have tried to build 3-4 times. Finally I settled on the following after looking at bjam --help.
This worked for me creating a c:\boost\boost_1_35_0\lib directory as the rest of the getting started document assumes. Actually the getting started doc has it under C:\Program Files\boost\boost_1_35_0\lib, but I like c:\boost\boost_1_35_0\lib better.
After the build you can delete the c:\boost\boost_1_35_0\bin.v2 directory to free up space.
To start I followed the big 'Get Boost' button on the right side of boost.org; thinking, 'That sure is obvious'. That link takes you to a download page with boost version 1.35.0 right at the top. It shows the new libs with 'Detail' and 'Download'. I took a few seconds to read the new libs section and clicked on download. This took me to sourceforge.net where they have the source code only release. Well, I knew that Boost Consulting has maintained an installer for Windows assuming you are using boost with Visual Studio. So I jumped over to their boost installer site, only to find that they don't have one yet for 1.35.0.
No problem, I'll just go back and grab the source code from sourceforge.net and follow the instructions in the getting started document. I kicked off the download and started looking for the getting started document. After a while, I figure I must be crazy, because I can't find it. I finally do a google search in order to find it. Still thinking I must have just missed it, I went back and followed every link on the right of the the main boost site. It is not under 'Introduction' or any other of the sections. I finally did locate it, it is on the main page on the left under 'GETTING STARTED'. Funny how you can look right past something like that.
So now I figure all I have to do is follow the getting started guide to build boost.
Step 1. Get Boost. I already did that. My download had already completed from sourceforge.net. I unziped it (actually un-7zed it) to c:\boost\boost_1_35_0\.
Step 2. Explain Boost Distribution. Ok, nothing new here.
Step 3. Header only libs. Right, header only libs are nice. Just compile and go. However, Boost.Thread among others need to be compiled.
Step 4. Build with a header only lib. Been there done that many times. There are sub-steps for building with Visual Studio. I always use MPC, so this is not useful to me. I plan to create a separate post or two about building boost applications with MPC. When you see how easy it is to use MPC with Boost, I doubt that you will use anything else.
Step 5. Building Boost libraries. Alright, here we go.
Step 5.1. Install Boost libraries. Yeah, thats what I wanted to do to start with. However, Boost Consulting has not yet put out an installer for 1.35.0.
Step 5.2. Build from source.
Step 5.2.1. Get bjam. I put the executable in c:\boost\boost_1_35_0\.
Step 5.2.2. Identify toolset. I want: msvc.
Step 5.2.3. Select a build directory. It says this is not necessary.
Step 5.2.4. Invoke bjam. This is where I got in trouble. I tried various combinations of commands/arguments to bjam. I must have tried to build 3-4 times. Finally I settled on the following after looking at bjam --help.
cd c:\boost\boost_1_35_0Seems like I should have included --toolset=msvc, but I forgot and it picked msvc-8.0 anyway.
bjam --build-type=complete --prefix="c:\boost\boost_1_35_0" install
This worked for me creating a c:\boost\boost_1_35_0\lib directory as the rest of the getting started document assumes. Actually the getting started doc has it under C:\Program Files\boost\boost_1_35_0\lib, but I like c:\boost\boost_1_35_0\lib better.
After the build you can delete the c:\boost\boost_1_35_0\bin.v2 directory to free up space.
Subscribe to:
Posts (Atom)