Boost C++ Libraries: Ticket #3130: Provide 'All' library https://svn.boost.org/trac10/ticket/3130 <p> 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. </p> <p> For simplicity boost should provide a 'libboost', which joins together all the libraries of boost. </p> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/3130 Trac 1.4.3 anonymous Wed, 03 Jun 2009 18:54:01 GMT <link>https://svn.boost.org/trac10/ticket/3130#comment:1 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/3130#comment:1</guid> <description> <p> Just to clarify (sorry), by 'library' I mean the .o / .so / .dylib files Boost generates for some libraries, such as wave, thread and graph. </p> </description> <category>Ticket</category> </item> <item> <dc:creator>viboes</dc:creator> <pubDate>Sat, 06 Jun 2009 14:55:30 GMT</pubDate> <title>component changed https://svn.boost.org/trac10/ticket/3130#comment:2 https://svn.boost.org/trac10/ticket/3130#comment:2 <ul> <li><strong>component</strong> <span class="trac-field-old">None</span> → <span class="trac-field-new">Building Boost</span> </li> </ul> Ticket Vladimir Prus Tue, 10 Nov 2009 07:06:39 GMT milestone changed https://svn.boost.org/trac10/ticket/3130#comment:3 https://svn.boost.org/trac10/ticket/3130#comment:3 <ul> <li><strong>milestone</strong> <span class="trac-field-old">Boost 1.40.0</span> → <span class="trac-field-new">To Be Determined</span> </li> </ul> <p> This is good idea, but might not happen for 1.42 </p> Ticket René Rivera Thu, 04 Mar 2010 16:04:01 GMT <link>https://svn.boost.org/trac10/ticket/3130#comment:4 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/3130#comment:4</guid> <description> <p> 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. </p> </description> <category>Ticket</category> </item> <item> <dc:creator>Steven Watanabe</dc:creator> <pubDate>Wed, 13 Mar 2013 16:55:49 GMT</pubDate> <title>status changed; resolution set https://svn.boost.org/trac10/ticket/3130#comment:5 https://svn.boost.org/trac10/ticket/3130#comment:5 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">wontfix</span> </li> </ul> Ticket