Ryan Schmidt <[email protected]> writes: > On Sep 12, 2013, at 03:40, Rainer M Krug wrote: > >> I have some binary installations from .pkg amd .dmg files, which require >> certain frameworks to be installed. Now some frameworks contain >> libraries which I also installed via homebrew. >> >> So my question: I understand, that the binary installations require >> these frameworks - but do these frameworks interfere with macports >> installations? > > Yes, if libraries, headers or frameworks are installed in standard > locations (/usr/local/lib, /usr/local/include and /Library/Frameworks, > respectively) then software (including software built with MacPorts) > might inadvertently find it, which could result in those libraries or > frameworks being used instead of MacPorts' versions, or features being > enabled that MacPorts did not intend to enable, which might possibly > lead to build failure. Therefore we do not support users installing > software in /usr/local or /Library/Frameworks.
Thanks for the clarification, Rainer > -- Rainer M. Krug email: RMKrug<at>gmail<dot>com _______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
