Using macports to create binary package

[Manav Bhatia]

I typically do:

$ port install openmpi-clang hdf5 eigen boost 

before building my application. This installs (a lot of) dependencies, including gcc. 

Thanks for pointing me to dylibbundler. I was not aware of that. I will look into the details of this package. 

Will this be able to take ports installed in a default /opt/local location and pack them in an app bundle? 

-Manav

> On Jul 20, 2018, at 9:53 AM, Craig Treleaven <ctreleaven at macports.org> wrote:
> 
>> On Jul 20, 2018, at 8:51 AM, Manav Bhatia <bhatiamanav at gmail.com <mailto:bhatiamanav at gmail.com>> wrote:
>> 
>> Thanks. 
>> 
>> I saw some instructions related to octave that describes creations of an app bundle that can be put anywhere: https://wiki.octave.org/Create_a_MacOS_X_App_Bundle_Using_MacPorts <https://wiki.octave.org/Create_a_MacOS_X_App_Bundle_Using_MacPorts>
>> 
>> One of the commands they used is install_name_tool: 
>> install_name_tool -change /opt/local/libiconv.2.dylib @executable_path/../lib/libiconv.2.dylib Octave-3.7.0+
>> 
>> So, if I only keep the specific header files and relevant dyld files, with enough care something like this should be possible (?). 
>> 
>> -Manav
>> 
> 
> Creating a Mac application bundle is a somewhat different objective from what I thought was your stated goal.  You haven’t said what you want to package.
> 
> If it is appropriate to package your app as an app bundle, then perhaps dylibbundler is what you need.  Check ‘port info dylibbundler’ and ‘port gohome dylibbundler’.
> 
> Craig

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20180720/6a4b6b05/attachment.html>