[Proj] PROJ as embeddable framework for Mac OS

[Hal Mueller]

On Jan 4, 2008, at 9:00 PM, William Kyngesburye wrote:
> As a small example, if you bundle the GDAL and PROJ frameworks.   
> GDAL also links to PROJ, so you would have to change the references  
> in the bundled GDAL to use the relative path to the bundled PROJ.   
> The more interdependent frameworks you bundle, the more changes  
> within those bundled frameworks are needed.

This sounds like an argument for using @executable_path in the  
frameworks in that case.

There are certainly cases where you want to install one copy of the  
Maptools frameworks in /Library, for all apps to share.  But there  
are other situations where you want to be independent of the  
installed environment.  So perhaps 2 different targets are needed-- 
one embeddable target, and one for system-level installation.

For the archives:  data directory ends up being /Library/Frameworks/ 
PROJ.framework/Resources/proj, for the current iteration anyway.

Resources/Info.plist, and the proj files themselves (in  
PROJ.framework/Resources/proj), are world-writeable, and owned by the  
user who installed them, with a group of "wheel".  I don't see this  
as much of a security risk, however.

Thanks for all of your work!

Hal