StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Agreed; <a href="http://www.boost.org/doc/libs/1_39_0" rel="noreferrer">the boost website</a> has good tutorials for the most part, broken down by sub-library. </p> <p>As for compiling, a good 80% of the library implementation is defined in the header files, making compiling trivial. for example, if you wanted to use shared_ptr's, you'd just add </p> <pre><code>#include <boost/shared_ptr.hpp> </code></pre> <p>and compile as you normally would. No need to add library paths to your g++ command, or specify -llibboost. As long as the boost directory is in your include path, you're all set.</p> <p>From the boost documentation:</p> <blockquote> <p>The only libraries that need to be compiled and linked are the following:The only Boost libraries that must be built separately are:</p> <ul> <li>Boost.Filesystem</li> <li>Boost.IOStreams</li> <li>Boost.ProgramOptions</li> <li>Boost.Python (see the Boost.Python build documentation before building and installing it)</li> <li>Boost.Regex</li> <li>Boost.Serialization</li> <li>Boost.Signals</li> <li>Boost.Thread</li> <li>Boost.Wave</li> </ul> <p>A few libraries have optional separately-compiled binaries:</p> <ul> <li>Boost.DateTime has a binary component that is only needed if you're using its to_string/from_string or serialization features, or if you're targeting Visual C++ 6.x or Borland.</li> <li>Boost.Graph also has a binary component that is only needed if you intend to parse GraphViz files.</li> <li>Boost.Test can be used in “header-only” or “separately compiled” mode, although separate compilation is recommended for serious use.</li> </ul> </blockquote> <p>So, if you're using one of the listed libraries, use the <a href="http://www.boost.org/doc/libs/1_39_0/more/getting_started/index.html" rel="noreferrer">Getting Started guide</a> to, well, get you started on compiling and linking to Boost.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload