[MacPorts] #22628: cairo configure fails due to odd fontconfig pkgconfig .pc file
MacPorts
noreply at macports.org
Fri Nov 20 22:46:31 PST 2009
#22628: cairo configure fails due to odd fontconfig pkgconfig .pc file
------------------------------+---------------------------------------------
Reporter: dbsgeo@… | Owner: ryandesign@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 1.8.1
Keywords: | Port: fontconfig
------------------------------+---------------------------------------------
Comment(by dbsgeo@…):
Yes, I'm sure they will, so feel free to close as invalid.
And, to be honest I'm doing something else which may be compounding the
issue.
I'm experimenting with compiling and linking cairo and cairo deps against
the system (snow leopard) provided zlib and libiconv. In this case the
goal is to package the cairo dylibs into a relocatable Framework for
distribution/packagmaker install. Previously I was happily packaging up
zlib and libiconv and all the other cairo/cairomm dependencies, but after
a review by other more experienced packagers it was recommended to not
bundle zlib and libiconv from macports since the system provides universal
libs already without XCode, so I've been (up to cairo at least)
successfully installing the universal variant of zlib and libiconv and
then overwriting all of the libs with a symlink to the system lib. Stuff
like libpng and freetype have been building fine and linking to the system
libs.
I'm certainly open to suggestions for smarter ways to do this, and I don't
want to cause any undu burden by creating tickets due to my odd setup. How
do others distribute macports built libs while compiling and linking to
system libs where appropriate? In this case install_name_tool won't work
because the major lib compatibility version of libiconv is different.
--
Ticket URL: <http://trac.macports.org/ticket/22628#comment:5>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list