Re: Can't copy packing into package
Re: Can't copy packing into package
- Subject: Re: Can't copy packing into package
- From: j o a r <email@hidden>
- Date: Sun, 15 Jun 2008 16:53:39 -0700
On Jun 15, 2008, at 1:52 PM, Trygve Inda wrote:
I drag my bundle into xcode and select "Create folder reference"
Then in my Copy Files step I tell it to put it in the Project
directory. It
doesn't put it anywhere.
I'm not sure exactly how you did that, but when I try to do something
similar, it works. That said, there is probably a better way to solve
this problem - See below.
My structure looks like:
[ ] Application
[ ] build
[ ] Release
[ ] myApp
[ ] Contents
[ ] PlugIns
[ ] myPlugIn1.plugin
[ ] myPlugIn1.data
[ ] myPlugIn1 (xcode project in here)
[ ] myPlugIn2
In myPlugIn1 Xcode project I have the output set to build it to the
above
structure and myPlugIn.data is within myPlugInBuild. I have set a
Copy Files
step to try and put it in the same output directory as the build,
but it
does not work.
The .plugin compiled output ends up in the right place, but I am
also trying
to copy a data file to the same location. It works if I use a script
and
unix copy tool, but not with Copy Files.
It seems that you try to "push" the plugin into the right place from
the plugin project, rather than "pulling" it into the product from the
application project? You should "pull" parts into their correct places
from the project of the product, not "push" them from other projects.
What you would typically do in this case is to add your plugin
projects as cross-project references from the application project.
Doing this will allow you to - in the application project itself - set
up standard target dependencies to [1] build the plugins before the
application, and then also to [2] copy the plugins into the application.
If you use cross-project references you wouldn't have to drag
references to the build products of your plugin targets from the
Finder, you would instead drag product references from the cross-
project target in the application projects Groups and Files pane to
the copy files phase in the application target.
Using cross-project references also supports multiple build
configurations, so that you get the correct Debug / Release version of
your plugins or the corresponding version of your application.
Note that if you're using Xcode 2.5 or 3.0 you have to use a shared
build folder for all projects that you build using cross-project
references.
I'm sorry if the above is not 100% clear and easy to understand. It's
not easy to describe it in writing, but very easy to show if we had
been sharing a screen...
j o a r
_______________________________________________
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