Re: Populating A Package's Library Folder
Re: Populating A Package's Library Folder
- Subject: Re: Populating A Package's Library Folder
- From: Peter Borg <email@hidden>
- Date: Thu, 5 Jan 2006 00:11:49 +0100
Hi!
Be sure to choose the "Create Folder References for any added folders"
when you add the folder (plug-in) to the project in Xcode. Then for
the settings for the Copy Files Phase choose e.g. Resources for the
Destination and "../Library/Spotlight" (note the two dots at the
beginning) for the Path. I don't know if this is the best/recommended
way of doing it, but it works.
Cheers,
Peter
On 1/4/06, Nick Nallick <email@hidden> wrote:
> The release version of my application contains a library folder for
> Automator and Spotlight plug-ins (i.e., MyApp.app/Contents/Library).
> What's the best way to create and populate this folder during a build?
>
> I've tried adding my spotlight and automator packages to my project
> and using a "copy files" build phase to do this, but the plug-in
> packages are added to my project as nested folders and "copy files"
> seems to be pretty literal in that it only recognizes files and not
> directories so I can't just copy an entire plug-in into my package
> with this build phase.
>
> FWIW, it looks like I can add CodeWarrior's package actions next to a
> property list compiler on my wish list of Xcode package building
> features.
>
> Thanks,
> Nick
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden