Opened 7 years ago
Last modified 7 years ago
#11781 new Bugs
b2 install not copying filesystem.hpp or program_options.hpp
| Reported by: | Owned by: | ||
|---|---|---|---|
| Milestone: | To Be Determined | Component: | Building Boost |
| Version: | Boost 1.59.0 | Severity: | Problem |
| Keywords: | Cc: |
Description
It is very possible I am doing something wrong, but I've been unable to get boost/filesystem.hpp and boost/program_options.hpp to be copied during the installation process with b2...
I've followed the easy setup instructions.
$ 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
Then simply doing an
$ 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
I've tried this with boost-1.59.0, boost-1.58.0 and boost-1.57.0, and nothing seems to fix it.
- After running
./b2 installshouldboost/filesystem.hppbe installed in the--prefixlocation? - If so, how can I get the package headers to install as I expect?
Change History (5)
comment:1 by , 7 years ago
| Type: | Support Requests → Bugs |
|---|
comment:2 by , 7 years ago
| Component: | None → Building Boost |
|---|
comment:3 by , 7 years ago
comment:4 by , 7 years ago
Thanks!
I had the same problem and the ./b2 headers worked.
This change seems strange to me... but ok!
comment:5 by , 7 years ago
The necessity of running b2 headers before install will eventually go away, when I finally get around to fixing it.
Note:
See TracTickets
for help on using tickets.

@vibes, this may actually be more of an issue with the documentation. I ended up figuring it out...
modular boost specific instructions state that this command is necessary:
Whereas, the standard install instructions do not give that direction.
My understanding is that modular-boost is the path forward, if that is the case, should the standard install instructions be updated?