linuxdcpp-team team mailing list archive

[Ximin Luo <xl269@xxxxxxxxx>]

> Not even MacPorts requires you to install its own GCC build in order
to install/install any MacPorts packages.

Installing MacParts GCC allows you to *build* MacPorts packages
automatically using `port`, or that was the case when we tried it. Also
Last time I checked, XCode used an old version of gcc (4.1?); some tools
require gcc 4.3 which is only available in MacPorts.

> MacPorts clearly says on its install page that XCode is one of its
requirements

This is for the MacPorts software *itself*, not its packages.

> any software claiming OS X compatibility, should be able to build with
it.

LinuxDC++ does not claim this.

> The point of MacPorts is not to supply an alternate universe with the
whole development toolchain

Not for normal users. However if you're a developer, making a MacPorts
package, you should be building stuff using the MacPorts toolchain.

> but rather to nicely plugin into the default OS X development
infrastructure (which is XCode).

No, this is not true. Why do you think they install everything in
/opt/local instead of the system folders??

-- 
MacPorts boost lib not detected on OS X
https://bugs.launchpad.net/bugs/481833
You received this bug notification because you are a member of LinuxDC++
Team, which is subscribed to LinuxDC++.

Status in Linux DC++: Fix Committed

Bug description:
Hi,

Tested with latest bzr repository, after installing all dependencies via MacPorts 1.8.1, 
this error remains when launching build with scons:
---
...
Checking for C++ header file boost/version.hpp... no
	boost not found.
	Note: You might have the lib but not the headers
---
boost headers *are* installed in /opt/local/include/boost/*, but it's not picked.
(all other MacPorts dependencies are recognized)

If I comment out the check in SConstruct and add -I/opt/local/include to CXXFLAGS, 
it builds correctly.