avoid usage of Macport installed software

Brandon Allbery allbery.b at gmail.com
Thu May 7 09:52:16 PDT 2015

On Thu, May 7, 2015 at 12:48 PM, petr <976F at ingv.it> wrote:

> I am working on some new port. It works already quite fine, but I observe
> that when using it without Tracemode, it would pick up various already
> installed programs. Most of these are also provided by Xcode, but notably
> when `doxygen` is picked up, it also creates some extra documentation. This
> all works smoothly, but it would not create a consistent build across
> various installs. Is there a canonical way to avoid such problems?

Depends on what build system it uses; for example autoconf-based things
often have --with-THING=/path / --without-THING.

That said, you should always use the MacPorts dependency (and add a
dependency on it), not the Xcode one.

brandon s allbery kf8nh                               sine nomine associates
allbery.b at gmail.com                                  ballbery at sinenomine.net
unix, openafs, kerberos, infrastructure, xmonad        http://sinenomine.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-dev/attachments/20150507/7294dcab/attachment.html>

More information about the macports-dev mailing list