Re: Building fxplug with shared libraries and static libraries
Re: Building fxplug with shared libraries and static libraries
- Subject: Re: Building fxplug with shared libraries and static libraries
- From: Darrin Cardani <email@hidden>
- Date: Mon, 11 Nov 2013 13:53:40 -0800
Sorry I wasn’t more clear. What I meant was that you can add a “Copy Files” build phase to copy the shared libraries into your built plug-in bundle’s Contents/Frameworks folder. This is in the “Build Phases” for each target. You can choose “Add Copy Files Build Phase…” from the “Editor” menu while you have the target’s “Build Phases” tab open in Xcode.
For static libraries, it should be enough just to add them to your Xcode project and link against them. Since they are static, the linker should do the right thing and copy them into your binary.
Darrin On Nov 11, 2013, at 1:24 PM, Ardo Avancena < email@hidden> wrote: The one of the shared libraries that I am using is dependent on the other libraries. All of the libraries that I added does not ship with the system. So does that mean I should just add them in the External Framework and Libraries group in my project? Or are you referring to something else?
And how do I compile the static library into my plug in?
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden