Adding MacPorts libraries to an Xcode project

[Ryan Schmidt]

Please continue to Cc the mailing list on your replies (by using Reply All) so that others can benefit from the discussion.


On Jul 6, 2020, at 18:29, Thomas Bodlien wrote:

>> I guess you have two choices:
>> 
>> 1. Don't use codesigning in your Xcode project
>> 2. Codesign the MacPorts libraries that you want to use
> 
> Hmm, the App has to be codesigned, because I want to release on the Mac App Store.

Yup, I understand.

> The MacPorts library is a dynlib /opt/local/lib/libdbus-1.3.dylib. What happens, if I sign and embed it and on MacPorts a new version will be released?

What do you mean by "embed"? If you mean you copy the dylib into your app bundle, fix its install_name and linkage to be relative, and then codesign that copy, then nothing will happen to the copy; it's yours.

But if you modify the dylib in its original location in /opt/local/lib for example by codesigning it, or in general if you make any modifications to files installed by a MacPorts port, and then you upgrade the port, your modifications will be lost.

> The DBUS daemon has to be installed by MacPorts.