<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
I need to reconfigure PROJ as an embeddable framework for Mac OS. This is so that I can make a drag-and-drop installable app (one that does not need an installer, as is recommended by current Apple guidelines). The binaries posted on the Kyngchaos site are built as system-wide frameworks. <div><br class="webkit-block-placeholder"></div><div>The Kyngchaos port has this tantalizing note in the ReadMe.rtf: </div><div><br class="webkit-block-placeholder"></div><div><blockquote type="cite" class=""><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="4" style="font: 14.0px Helvetica"><span class="Apple-style-span" style="font-size: 13px; -webkit-text-stroke-width: -1; "><font face="Helvetica" size="4" style="font: 14.0px Helvetica">Before linking (or maybe after linking) the framework copy's install_name and library paths should be changed using </font><font face="Monaco" size="3" style="font: 12.0px Monaco">install_name_tool</font><font face="Helvetica" size="4" style="font: 14.0px Helvetica">. A handy relative path that can be used is </font><font face="Monaco" size="3" style="font: 12.0px Monaco">@executable_path</font><font face="Helvetica" size="4" style="font: 14.0px Helvetica">, this is the location of the app executable. </font></span>So a path to the framework within the app package would be </font><font face="Monaco" size="3" style="font: 12.0px Monaco">@executable_path/../Frameworks/PROJ.framework/PROJ</font><font face="Helvetica" size="4" style="font: 14.0px Helvetica">.</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 14px/normal Helvetica; min-height: 17px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="4" style="font: 14.0px Helvetica">You would have to change the id of the framework, and the dependencies of the framework that are also included in the app package, to be relative paths. This can get messy.</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 14px/normal Helvetica; min-height: 17px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="4" style="font: 14.0px Helvetica">Currently there is an additional consideration: the data folder. It is normally hardwired into the library, but there is also an environment variable to override that. It's up to the programs using PROJ to take care of this.</font></div></blockquote><br></div><div>What exactly do I need to pass as arguments to install_name_tool? What -id am I working with?</div><div><br class="webkit-block-placeholder"></div><div>What are the "messy" dependencies referred to?</div><div><br class="webkit-block-placeholder"></div><div>What change do I need to make to manage the data folder? What's the default as built?</div><div><br class="webkit-block-placeholder"></div><div>This would be a lot easier to understand if the build instructions were included in the framework. Or are they now included if I do a configure/build on the Mac?</div><div><br class="webkit-block-placeholder"></div><div>Hal</div><div><br class="webkit-block-placeholder"></div></body></html>