[MacPorts] #37207: bad include paths?
MacPorts
noreply at macports.org
Wed Dec 5 05:13:01 PST 2012
#37207: bad include paths?
------------------------+--------------------------------
Reporter: jshanab@… | Owner: macports-tickets@…
Type: defect | Status: closed
Priority: Normal | Milestone:
Component: ports | Version: 2.1.2
Resolution: invalid | Keywords:
Port: boost |
------------------------+--------------------------------
Changes (by cal@…):
* status: new => closed
* type: request => defect
* resolution: => invalid
* port: => boost
Comment:
MacPorts does not install into `/usr/local` (unless you manually
configured it to do so, and it'll give you a hard time if you try it) and
especially not into `/usr/local/boost`. I assume whatever you are
describing are not files installed by MacPorts and will thus close the
ticket as invalid.
MacPorts sticks to the filesystem hierarchy standard and installs headers
in `$prefix/include`, e.g. the boost headers would be in
`$prefix/include/boost` (1). It is indeed not possible to use boost from
MacPorts but ignore other include files in `$prefix/include`.
(1) See
http://packages.macports.org/boost/boost-1.52.0_1+no_single+no_static+python27.darwin_12.x86_64.tbz2
to get a list of files installed by the boost port in MacPorts.
--
Ticket URL: <https://trac.macports.org/ticket/37207#comment:2>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list