some questions about Boost libraries

[vladimir_prus]

I don't think that the need to add libraries to linker path is the problem specific to Boost? Pretty much any other third party library will be affected by this inconvenience. You certainly can move all libraries to the standard directory where Visual Studio keeps libs.

As for you second point -- are you specifically asking for ISO image that you can burn to CD, and that contains prebuilt libraries? This suggestion was not previously raised by users, I'll keep this in mind.

[CornedBee]

Here's what I do when I install a new Boost version for VC++. I can't guarantee that it will work for you, but it should.

1) Download the source archive.
2) Extract the source archive, e.g. to C:\boost (I don't do that, but it's easier to type).
3) Start a VC-enabled console (there's an option in the Tools menu)
4)

C:
cd \boost
bootstrap
bjam --built-type=complete --without-python msvc stage

5) Wait. A long time.
6) In VS, choose Tools->Options->Projects->VC++ Directories->Include Directories, and add C:\boost.
7) In the Library Directories sibling, add C:\boost\stage\lib
8) Party.

I've never had any problems with this sequence.

[Masterx]

I don't think that the need to add libraries to linker path is the problem specific to Boost? Pretty much any other third party library will be affected by this inconvenience. You certainly can move all libraries to the standard directory where Visual Studio keeps libs.

As for you second point -- are you specifically asking for ISO image that you can burn to CD, and that contains prebuilt libraries? This suggestion was not previously raised by users, I'll keep this in mind.

for the first part ok , i'll do sth about that , and yes i dont think either ( and i think i've already said that , this might be due to the wrong procedure i took to compile /build boost . )

and about that ISO. yes thats exactly what i mean .
and Thanks a Quadrillion to you and your boost associates for bringing us this great gift . keep up the great work .

Here's what I do when I install a new Boost version for VC++. I can't guarantee that it will work for you, but it should.

1) Download the source archive.
2) Extract the source archive, e.g. to C:\boost (I don't do that, but it's easier to type).
3) Start a VC-enabled console (there's an option in the Tools menu)
4)

C:
cd \boost
bootstrap
bjam --built-type=complete --without-python msvc stage

5) Wait. A long time.
6) In VS, choose Tools->Options->Projects->VC++ Directories->Include Directories, and add C:\boost.
7) In the Library Directories sibling, add C:\boost\stage\lib
8) Party.

I've never had any problems with this sequence.

tanx dear cornedBee , i'll give it a try . hope this one works for me ,
and in case it dont, i come to the conclusion that , sth must be wrong with my Visual Studio 2008! may be a reinstallation would be necessary .

[Mario F.]

for the first part ok , i'll do sth about that , and yes i dont think either ( and i think i've already said that , this might be due to the wrong procedure i took to compile /build boost . )

Your error has nothing to do with how you build the boost libraries. Guess I'm being ignored and I have better things to do.

Good luck.

[Masterx]

Your error has nothing to do with how you build the boost libraries. Guess I'm being ignored and I have better things to do.

Good luck.

nope, first of all i didnt mean to disrespect you or ignore you dear mariof .
i referred to my previous guess to complement vladimir_prus's idea on the library itself , and needless to say this conversation is supposed to be indicating to my previous post on building , the one before your first post ( i guess).
i do really appreciate the time you spent to help me and well i really do thank you,
so all i wana say is just dont get it wrong .
i dont like misunderstanding , cheer up bro .
again thank you all .

[Mario F.]

No worries. I may have released more air than I should. So my apologies too.

In a nutshell, Boost can be built in numerous ways (I'll add one more: From within Visual Studio IDE). From your previous efforts it is clear they have been already:

i did what you told me to.[...] decompressed the boost source codes , and before doing anything , i used .\bjam --clean
nothing happened! and then started the instructions as told .

So the libraries have been built and they exist. They are located under a "lib" folder inside the path you used for the --prefix bjam parameter.

When you then write your code and include any header requiring these compiled libraries, it will not suffice to simply add the library name to the linker options. You need to tell the linker where it should look for that filename.

Now under gcc (I'm assuming you are using gcc, right?) you can do this in one of 2 ways:

- Add the path to your system environment variables. Create a new environment variable (if it doesn't exist already) called LIBRARY_PATH and add to it any paths to compiled library files. It works just like your PATH variable; i.e. add paths separating them with a semi-colon.

- Or, give the fully qualified path (drive:\full_path_to_library\library_name.extensio n) to the linker options.

Your IDE may also give you the option to instruct the linker to search for libraries in a path defined by you. Without entering into much details, this is slightly different from the first option above (internally it will link against your library with the -L option instead of -l).

So, that's really the only think missing from your Boost adventure.

...

As for the many ways to build boost, they are mostly a matter of preference. I personally like to keep all my external libraries under a root folder named dev. And I like to keep this folder structure as clean as possible. Hence why I like to use --prefix=c:\dev\boost which allows me to instruct bjam where I want boost to go, and I like the install option over stage (because it will install on --prefix both the compiled libraries and all the header files).

So for every person you may hear a different story. However what is important is to know that the libraries have been built and where are they so you ca instruct your linker where to look for them.

[Masterx]

hello all .
its me again!
recently i was trying to install the latest version of boost! 1.44! under win7!
to cut a long story short! : i simply cant get it to compile! it gives me the errors:

F:/Boost/boost_1_44_0/tools/build/v2/build\feature.jam:320: in validate-feature from module feature
error: unknown feature "<install--build-type>"
F:/Boost/boost_1_44_0/tools/build/v2/build\feature.jam:354: in expand-subfeatures-aux from module feature
F:/Boost/boost_1_44_0/tools/build/v2/build\feature.jam:419: in feature.expand-subfeatures from module feature
F:/Boost/boost_1_44_0/tools/build/v2/build\build-request.jam:20: in apply-to-property-set from module build-request
F:/Boost/boost_1_44_0/tools/build/v2/kernel\modules.jam:103: in modules.call-in from module build-request
F:/Boost/boost_1_44_0/tools/build/v2/util\sequence.jam:48: in sequence.transform from module sequence
F:/Boost/boost_1_44_0/tools/build/v2/build\build-request.jam:32: in build-request.expand-no-defaults from module build-request
F:/Boost/boost_1_44_0/tools/build/v2\build-system.jam:623: in load from module build-system
F:\Boost\boost_1_44_0\tools\build\v2/kernel\modules.jam:283: in import from module modules
F:\Boost\boost_1_44_0\tools\build\v2\kernel\bootst rap.jam:142: in boost-build from module
F:\Boost\boost_1_44_0\boost-build.jam:17: in module scope from module

---------------------------------------------
Ok . now to be precise , i did the following! :
unpacked the Boost source code to :

F:\Boost\Boost_1_44_0

so everything resides in that boost_1_44_0 folder i wrote
then fired up my cmd ! and after navigating to the mentioned path above , typed in :

bootstrap.bat

then typed!:

bjam --toolset=gcc "--prefix=F:\Program Files\CodeBlocks\Boost" install--build-type=complete

then got:
couple of

"g++ is not recognized as an internal or external command,operable program or batch file!"

(actually 4 of these!)
then got:

F:/Boost/boost_1_44_0/tools/build/v2/build\feature.jam:320: in validate-feature from module feature
error: unknown feature "<install--build-type>"
F:/Boost/boost_1_44_0/tools/build/v2/build\feature.jam:354: in expand-subfeatures-aux from module feature
F:/Boost/boost_1_44_0/tools/build/v2/build\feature.jam:419: in feature.expand-subfeatures from module feature
F:/Boost/boost_1_44_0/tools/build/v2/build\build-request.jam:20: in apply-to-property-set from module build-request
F:/Boost/boost_1_44_0/tools/build/v2/kernel\modules.jam:103: in modules.call-in from module build-request
F:/Boost/boost_1_44_0/tools/build/v2/util\sequence.jam:48: in sequence.transform from module sequence
F:/Boost/boost_1_44_0/tools/build/v2/build\build-request.jam:32: in build-request.expand-no-defaults from module build-request
F:/Boost/boost_1_44_0/tools/build/v2\build-system.jam:623: in load from module build-system
F:\Boost\boost_1_44_0\tools\build\v2/kernel\modules.jam:283: in import from module modules
F:\Boost\boost_1_44_0\tools\build\v2\kernel\bootst rap.jam:142: in boost-build from module
F:\Boost\boost_1_44_0\boost-build.jam:17: in module scope from module

so what is wrong with who! ? me , boost , windows7 ?
and how can i get this to work!
( im planning to download the prebuild library for visual studio 2008! , so i just need to get this to work with CB!)
by the way dont we have any prebuild libs for CB yet ?
thanks in advance

[rags_to_riches]

install--build-type=complete

That doesn't look like the right options. Look at the example in the docs:

bjam --build-dir=build-directory toolset=toolset-name --build-type=complete stage

[Masterx]

install--build-type=complete

That doesn't look like the right options. Look at the example in the docs:

bjam --build-dir=build-directory toolset=toolset-name --build-type=complete stage

thank you brother , its compiling now .
i made a mistake a year a go while writing down the build instructions for further uses ,after i made it through by this thread ,.
its really a surprising coincidence that i had the exact problem in exact time in! a year ago! !

[Masterx]

and oh , by the way , according to this i was right in compiling procedure for boost !(which failed! guess thats different now for 1.44)
and another irony is that when i typed :

bjam "--prefix=F:\Program Files\CodeBlocks\Boost" --toolset=gcc--build-type=complete

instead of making a folder in CodeBlocks directory! and place the libs there! it placed them in F:\Boost\Boost_1_44_0! , as if i didnt provide any path!
any explanation for this too?

[Fordy]

I usually seem to have a bad time compiling the boost libs too...

I'm using them on ubuntu at the moment, to get them going on that OS takes a single "apt-get" command!

[Masterx]

I usually seem to have a bad time compiling the boost libs too...

I'm using them on ubuntu at the moment, to get them going on that OS takes a single "apt-get" command!

lucky you , i 've never had such a joy , i envy you man (T_T)
i really need to compile it badly
i dont know why there are such hassles in compiling a library , really?(o_O)
why not be any prebuild Iso ? whats the problem of that! or atleast providing a hassle free procedure !?
i hope i make it at last.
seems to me no matter what experience i gained a year ago in compiling boost , i had to repeat history each time for each freaking version! (><)
again would anyone who uses CB and has compiled Boost ( 1.44) under win7,tell me how he/she did make it ?

[laserlight]

why not be any prebuild Iso ? whats the problem of that! or atleast providing a hassle free procedure !?

But there are pre-built binaries provided by BoostPro, except that you rejected them back in post #7.

[Masterx]

But there are pre-built binaries provided by BoostPro, except that you rejected them back in post #7.

i already downloaded the installer and im planning to use that for MS VS2008!
i couldn't find any other prebuild binaries you are talking about. there is only one prebuild package and thats only for MS Visual Studio as far as i know .( would appreciate you if you let me know which if there is another prebuild packages for other compilers)!
anyways , so all said im back at where i started a year ago (><) this time under win7! with newer build! and with the walk-through on CB's wiki not working at all! (><)

[Elysia]

Shouldn't just
bjam toolset=gcc
work?

I have compiled boost some times, but I never have had to specify a path or prefix.
I typically just do

bjam variant=debug,release link=static address-model=32,64

(Note that this is not my exact line, so it's not tested!)

And everything sorts itself out.