Alexander Hansen wrote: > (adding jfm back) > > Daniel Macks wrote: > >> On Thu, Jun 25, 2009 at 08:27:10PM +0200, Alexander Hansen wrote: >> >> >>> Jean-Fran?ois Mertens wrote: >>> >>> >>>> Too lazy to try fixing this cmake stuff.. (sure there must be a way, >>>> either to fix >>>> the flag-ordering, or to change compiler and linker); so, dirty >>>> solution : >>>> Adding to the patchscript the lines >>>> >>>> >>>> >>>>> echo '#!/bin/sh -ev >>>>> name=`basename $0` >>>>> flag-sort -v /usr/bin/$name $@' >> ../c++ >>>>> chmod a+x ../c++ >>>>> ln ../c++ ../cc >>>>> >>>>> >> I *think* that last line should be "ln c++ ../cc" (otherwise ../cc >> points to ../../c++), but otherwise seems fine. >> >> >> > This is a hard link, though; so I wouldn't think the paths should > matter, since 'c++' doesn't _point_ to 'cc' but rather is a _copy of_ > 'cc'. At least that's how it worked when I was playing around with it. > >>>> and changing the PATH line to : >>>> >>>> >>>> >>>>> export PATH="%b/..:$QTDIR/bin:%p/lib/freetype219/bin:$PATH" >>>>> >>>>> >> If this idiom is popular, would be easy enough to add a pile of cc and >> c++ (and gcc and g++) wrappers in a bindir as part of flag-sort. >> >> Unrelatedly, if your BDep:freetype219 is >= 2.3.7-7, you do not need >> special PATH (or any other) flags or variables to find ft219. And if >> you are Dep/BDep >= 2.3.8-2, you also avoid some freetype219 >> backwards-incompatible ABI breakage. >> >> dan >> >> >> > I'm not sure if the freetype219 path is even needed here. The package > doesn't carry a direct dependency on freetype219 (and doesn't link to it). > > belay that. It finds X11's freetype2 by default.
-- Alexander Hansen Fink User Liaison ------------------------------------------------------------------------------ _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel
