Opened 13 years ago
Closed 10 years ago
#3130 closed Feature Requests (wontfix)
Provide 'All' library
Reported by: | Owned by: | ||
---|---|---|---|
Milestone: | To Be Determined | Component: | Building Boost |
Version: | Boost 1.39.0 | Severity: | Problem |
Keywords: | Cc: |
Description
At the moment, users have to worry about which libraries to link in, depending on what they are using. This involves them looking up which parts of boost need a library, and which don't.
For simplicity boost should provide a 'libboost', which joins together all the libraries of boost.
Change History (5)
comment:1 by , 13 years ago
comment:2 by , 13 years ago
Component: | None → Building Boost |
---|
comment:3 by , 13 years ago
Milestone: | Boost 1.40.0 → To Be Determined |
---|
This is good idea, but might not happen for 1.42
comment:4 by , 13 years ago
Providing such a universal single lib build would introduce a library naming compatibility problem. If the same library name can be configured to include different permutations of the Boost libraries then one would get rather bad link problems. Hence we would have to tag the library produced with something indicating which libs it includes. And obviously just listing which libs used is horrible, as it would produce rather long names. Which leaves having some sort of hash as a tag.
comment:5 by , 10 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Just to clarify (sorry), by 'library' I mean the .o / .so / .dylib files Boost generates for some libraries, such as wave, thread and graph.