How t ouse external frameworks

[Ryan Schmidt]

On Mar 6, 2011, at 17:00, M-Rick wrote:
> Le 6 mars 2011 à 21:43, Rainer Müller a écrit :
>> On 2011-03-06 21:30 , M-Rick wrote:
>>> I would need to compile some ports using external frameworks stored in /Library/Frameworks.
>>> 
>>> How can I tell Macports to check this path ?
>>> 
>>> I tried to put in in PATH variables, but it doesn't seem to care about it.
>> 
>> Sorry, but that's not supported:
>> 
>> http://trac.macports.org/wiki/FAQ#syslibs
>> http://trac.macports.org/wiki/FAQ#ownlibs
>> 
>> What kind of ports are these? Portfiles you created on your own outside
>> of the official tree? In this case you could add the path in the
>> specific Portfile. Ports in our tree should bring all required
>> dependencies with them.
> 
> Yes they are made from portfiles coming from the official tree but build with a special path and cleaned without the unneeded libraries and files. My aim is to have in a special and appropriate location once, a set of libraries that I can update easily with MacPorts, then built several port from Macport, over this set just once.
> 
> For example, to make it simple, let's say I would like just once libjpeg and its dependencies built once, stored in the path /Library/Frameworks/jpeg.framework and then I want to build 3 or 4 applications that will connect over my jpeg.framework i previously built.

Well, if you would use MacPorts without modification, you would get just a single copy of libjpeg (it has no dependencies) in /opt/local/lib. It would be built as a dynamic library, not as a Mac OS X framework. This is not sufficient for you?