Boost C++ Libraries: Ticket #11781: b2 install not copying filesystem.hpp or program_options.hpp https://svn.boost.org/trac10/ticket/11781 <p> It is very possible I am doing something wrong, but I've been unable to get <code>boost/filesystem.hpp</code> and <code>boost/program_options.hpp</code> to be copied during the installation process with <code>b2</code>... </p> <p> I've followed the <a href="http://www.boost.org/doc/libs/1_59_0/more/getting_started/unix-variants.html#easy-build-and-install">easy setup instructions</a>. </p> <pre class="wiki">$ cd modular-boost $ ./bootstrap.sh --prefix=/opt/boost $ ./b2 stage ... The Boost C++ Libraries were successfully built! The following directory should be added to compiler include paths: /home/user/Projects/modular-boost The following directory should be added to linker library paths: /home/userProjects/modular-boost/stage/lib $ sudo ./b2 install --prefix=/opt/boost </pre><p> Then simply doing an </p> <pre class="wiki">$ ls /opt/boost/include/boost/filesystem/ config.hpp convenience.hpp detail exception.hpp fstream.hpp operations.hpp path.hpp path_traits.hpp $ ls /opt/boost/include/boost/filesystem.hpp ls: cannot access /opt/boost/include/boost/filesystem.hpp: No such file or directory </pre><p> I've tried this with boost-1.59.0, boost-1.58.0 and boost-1.57.0, and nothing seems to fix it. </p> <ul><li>After running <code>./b2 install</code> should <code>boost/filesystem.hpp</code> be installed in the <code>--prefix</code> location? </li><li>If so, how can I get the package headers to install as I expect? </li></ul> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/11781 Trac 1.4.3 anonymous Mon, 02 Nov 2015 01:38:21 GMT type changed https://svn.boost.org/trac10/ticket/11781#comment:1 https://svn.boost.org/trac10/ticket/11781#comment:1 <ul> <li><strong>type</strong> <span class="trac-field-old">Support Requests</span> → <span class="trac-field-new">Bugs</span> </li> </ul> Ticket viboes Sat, 21 Nov 2015 20:36:41 GMT component changed https://svn.boost.org/trac10/ticket/11781#comment:2 https://svn.boost.org/trac10/ticket/11781#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 gtmalmgren@… Sat, 21 Nov 2015 21:33:37 GMT <link>https://svn.boost.org/trac10/ticket/11781#comment:3 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/11781#comment:3</guid> <description> <p> @vibes, this may actually be more of an issue with the documentation. I ended up figuring it out... </p> <p> <a class="ext-link" href="https://svn.boost.org/trac/boost/wiki/TryModBoost#InstallingModularBoost"><span class="icon">​</span>modular boost specific instructions</a> state that this command is necessary: </p> <pre class="wiki">./b2 headers </pre><p> Whereas, the <a href="http://www.boost.org/doc/libs/1_59_0/more/getting_started/unix-variants.html#or-build-custom-binaries">standard install instructions</a> do not give that direction. </p> <p> My understanding is that modular-boost is the path forward, if that is the case, should the standard install instructions be updated? </p> </description> <category>Ticket</category> </item> <item> <author>albert.gil@…</author> <pubDate>Tue, 24 Nov 2015 21:47:07 GMT</pubDate> <title/> <link>https://svn.boost.org/trac10/ticket/11781#comment:4 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/11781#comment:4</guid> <description> <p> Thanks! I had the same problem and the <code>./b2 headers</code> worked. This change seems strange to me... but ok! </p> </description> <category>Ticket</category> </item> <item> <dc:creator>Steven Watanabe</dc:creator> <pubDate>Sat, 13 Feb 2016 21:28:15 GMT</pubDate> <title/> <link>https://svn.boost.org/trac10/ticket/11781#comment:5 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/11781#comment:5</guid> <description> <p> The necessity of running b2 headers before install will eventually go away, when I finally get around to fixing it. </p> </description> <category>Ticket</category> </item> </channel> </rss>