Re: [Boost-users] Which boost libraries need libs?

IMHO as a complete newcomer to Boost I was also keen to find out this information. If, like me, you are having trouble building the libraries, it's good to know that there is still a lot of very useful stuff in the headers alone. A note in the "Getting Started" section listing the libraries that need building, and saying that everthing else only requires the appropriate headers to be included might help encourage in a few extra users to put a toe in the water. Regards Jim Douglas "Aaron Griffin" wrote in message news:d64a489805092612316ccc0049@mail.gmail.com...

On 9/26/05, Richard Kaiser wrote:

...

Can anybody tell me, which of the Boost libraries need libs (usually created with bjam)?

As far as I can see, for most of the Boost libraries source code #includes are sufficient. For them, installation step 1 from the "Getting Started"-page is sufficient. Or do I get something wrong?

If you build the whole shebang from scratch you can see which libraries need libs and which don't.

In addition, you can look at this file list here: http://archlinux.org/packages.php?op=files&id=5997

The /usr/lib entries will have all the libs with a standard boost build.... I did the hard work for you... the following libraries require .so/.a libraries: boost_date_time boost_filesystem boost_iostreams boost_prg_exec_monitor boost_program_options boost_python boost_regex boost_serialization boost_signals boost_test_exec_monitor boost_thread boost_unit_test_framework boost_wave boost_wserialization