[Newbie Inquiry] Setting Library Path Settings in VC71
Hello Everyone, I needed a regular expression library, and having discovered Boost through google, I downloaded and installed it. I've set the environment for the include files by Tools > Options > Projects > VC++ Directories > Include Files. And I have set it to include a particular library file but the path goes something like this: "$(VCInstallDir)boost\bin\boost\libs\regex\build\libboost_regex.lib\vc-7_1\debug\runtime-link-static" I have a feeling something is wrong here. Is there a way to set the environment for the library files in one go without having to include another path each time I need some library file that isn't in my list of included paths? For example, if I needed a library file from "signals", I guess I would have to locate the appropriate file and then just enlist another path like "$(VCInstallDir)boost\bin\boost\libs\signals\build\..." Thanks.
I have a feeling something is wrong here. Is there a way to set the environment for the library files in one go without having to include another path each time I need some library file that isn't in my list of included paths?
Take another look at the getting started docs, you can either do an install: the lib files get copied to a location of your choice, or you can do a: bjam stage in which case the lib files are collected under boost-path/stage/lib Clear? John.
"John Maddock" wrote
Take another look at the getting started docs, you can either do an install: the lib files get copied to a location of your choice, or you can do a:
bjam stage
in which case the lib files are collected under boost-path/stage/lib
Clear?
You know, reading the introduction to http://www.boost.org/more/getting_started.html it really isnt very clear to me. Maybe it would help to provide a slightly gentler opening, a bit of preamble and some explanation of where we are and what we are about to do? Maybe something like : **Introduction** Welcome, The Boost distribution comprises numerous high quality C++ libraries and tools. Some libraries in the distribution are designed to be used header only while others are designed to be precompiled as static or dynamically linked libraries. Whichever operating system you are using, the suggested method of configuring the distribution, after it has been downloaded, is to invoke Boost Jam, a front end for the Boost Build system. A Bjam script is included with the distribution which can be used to build the static and dynamic libraries in the distribution and, optionally, copy both the headers and static and dynamically linked libraries into common directories of your choice, where they can be found by your compiler and linker. The following sections are designed to walk you in detail through getting, building, and installing the Boost distribution. 1.. Download Boost. 2.. Install Boost.Jam. 3.. Configure your compiler toolset. 4.. Go to Boost distribution directory. 5.. Build and install. ...etc regards Andy Little
"Andy Little" wrote
You know, reading the introduction to http://www.boost.org/more/getting_started.html it really isnt very clear to me.
[...] Following my previous post on this subject. It appears that having downloaded boost_1_33_1, then clicking the links "Getting Started" and "Getting Started Guide" on the main index page does absolutely nothing in IE6, no change from the index page, no error message, nothing... most strange. This may have something to do with my IE6 settings, but my setup works fine with boost_1_33_0. Everything works in Firefox though. Once having manually opened <more/getting_started.html> ( http://www.boost.org/more/getting_started.html ) and heading for the section headed Preparation, I was intrigued by the link to "build bjam from sources" (http://www.boost.org/tools/build/jam_src/index.html#building_bjam) Once there , I am presented with this text, the first line of which is like hitting me with a sledge hammer AFAICS, when I go WHAT??? -------------------------- *Building Boost.Jam* Installing BJam after building it is simply a matter of copying the generated executables someplace in your PATH. For building the executables there are a set of build bootstrap scripts to accomodate particular environments. The scripts take one optional argument, the name of the toolset to build with. When the toolset is not given an attempt is made to detect an available toolset and use that. The build scripts accept these areguments: <build script name> [toolset] Running the scripts without arguments will give you the best chance of success. On Windows platforms from a command console do: cd <jam source location> .\build.bat On Unix type platforms do: cd <jam source location> sh ./build.sh For the Boost.Jam source included with the Boost distribution the <jam source location> is BOOST_ROOT/tools/build/jam_src. If the scripts fail to detect an appropriate toolset to build with your particular toolset may not be auto-detectable. In that case, you can specify the toolset as the first argument, this assumes that the toolset is readily available in the PATH. NOTE: The toolset used to build Boost.Jam is independent of the toolsets used for Boost.Build. Only one version of Boost.Jam is needed to use Boost.Build. The supported toolsets, and wether they are auto-detected, are: ------------------------ In line with my remarks in the previous post I propose the changed text: ----------------------------- *Building Boost.Jam* The location for the Boost.Jam source files included with the Boost distribution is < [**link to** BOOST_ROOT] /tools/build/jam_src>. Also provided in the above Boost.Jam source directory are a set of build bootstrap scripts that can be used to build the Boost.Jam executable (called bjam.exe) in particular environments . Note: The scripts can take one optional argument. See *Building Boost.jam - Troubleshooting* for more information, but running the scripts without arguments will give you the best chance of success... On Windows platforms from a command console do: cd <jam source location> .\build.bat On Unix type platforms do: cd <jam source location> sh ./build.sh Installing BJam after building it is simply a matter of copying the generated executables someplace in your PATH. *Building Boost.jam - Troubleshooting* If the build scripts fail to detect an appropriate toolset to build with your particular toolset may not be auto-detectable. The scripts take one optional argument, the name of the toolset to build with.: <build script name> [toolset] In that case, you can specify the toolset as the first argument, this assumes that the toolset is readily available in the PATH. NOTE: The toolset used to build Boost.Jam is independent of the toolsets used for Boost.Build. Only one version of Boost.Jam is needed to use Boost.Build. The supported toolsets, and whether they are auto-detected, are: etc -------------------------- BTW It would be nice if all mentions of BOOST_ROOT in the docs were links explaining what it is again and again and again... All in all after looking through the getting started docs I believe the combination is why so many people have problems installing Boost! Apologies about all the criticism, but "getting started" is quite important isnt it? But as for the Windows Boost installer. It looks Great! Especially as it shows how useful a GUI is ;-) .. However I would recommend downloading only the distro and then building locally as downloading all the binaries can take an awfully long time. I gave up after an hour and cancelled it FWIW. regards Andy Little
"Andy Little" <andy@servocomm.freeserve.co.uk> writes:
Apologies about all the criticism, but "getting started" is quite important isnt it?
Yes, I've been planning to write a new getting started document for the 1.34 release, FWIW. -- Dave Abrahams Boost Consulting www.boost-consulting.com
"David Abrahams" <dave@boost-consulting.com> wrote in message news:uiro3fu3j.fsf@boost-consulting.com...
"Andy Little" <andy@servocomm.freeserve.co.uk> writes:
Apologies about all the criticism, but "getting started" is quite important isnt it?
Yes, I've been planning to write a new getting started document for the 1.34 release, FWIW.
hmmm... Now if there was a [Help] button on the Windows Installer, then you could be reading the docs while waiting for the binaries to download! Just a thought ! regards Andy Little
"Andy Little" <andy@servocomm.freeserve.co.uk> writes:
"David Abrahams" <dave@boost-consulting.com> wrote in message news:uiro3fu3j.fsf@boost-consulting.com...
"Andy Little" <andy@servocomm.freeserve.co.uk> writes:
Apologies about all the criticism, but "getting started" is quite important isnt it?
Yes, I've been planning to write a new getting started document for the 1.34 release, FWIW.
hmmm... Now if there was a [Help] button on the Windows Installer, then you could be reading the docs while waiting for the binaries to download!
Just a thought !
?? The whole point of the installer is that you don't need (the vast majority of) those instructions. -- Dave Abrahams Boost Consulting www.boost-consulting.com
"David Abrahams" wrote
"Andy Little" writes:
hmmm... Now if there was a [Help] button on the Windows Installer, then you could be reading the docs while waiting for the binaries to download!
Just a thought !
?? The whole point of the installer is that you don't need (the vast majority of) those instructions.
I was thinking more in terms of browsing the Boost libraries documentation. That of course implies that the docs were downloaded first! regards Andy Little
"Andy Little" <andy@servocomm.freeserve.co.uk> writes:
But as for the Windows Boost installer. It looks Great! Especially as it shows how useful a GUI is ;-) .. However I would recommend downloading only the distro and then building locally as downloading all the binaries can take an awfully long time. I gave up after an hour and cancelled it FWIW.
I think you should be more selective and not download everything. Trying to do a local build could be a bit harder, as it requires being able to properly configure the tools. We might add that option for Boost 1.34, though. -- Dave Abrahams Boost Consulting www.boost-consulting.com
?? ? wrote:
Hello Everyone,
I needed a regular expression library, and having discovered Boost through google, I downloaded and installed it. I've set the environment for the include files by Tools > Options > Projects > VC++ Directories > Include Files. And I have set it to include a particular library file but the path goes something like this: "$(VCInstallDir)boost\bin\boost\libs\regex\build\libboost_regex.lib\vc-7_1\debug\runtime-link-static" I have a feeling something is wrong here. Is there a way to set the environment for the library files in one go without having to include another path each time I need some library file that isn't in my list of included paths?
For example, if I needed a library file from "signals", I guess I would have to locate the appropriate file and then just enlist another path like "$(VCInstallDir)boost\bin\boost\libs\signals\build\..."
Thanks.
By running bjam with the "stage" or "install" targets, you can make it collect all library files into a single directory. Sebastian Redl
bjam stage and/or bjam install Then add the stage or install directory[0] to your lib path. [0] C:\Boost\lib is the default install directory; read the documentation for how to change this. Dale
participants (6)
-
?? ? -
Andy Little -
Dale McCoy -
David Abrahams -
John Maddock -
Sebastian Redl