Re: AppleScript as resource (and/or subproject product)
Re: AppleScript as resource (and/or subproject product)
- Subject: Re: AppleScript as resource (and/or subproject product)
- From: Nathan Vander Wilt <email@hidden>
- Date: Sat, 17 Oct 2009 12:51:39 -0700
On Oct 17, 2009, at 10:23 AM, Nathan Vander Wilt wrote:
My app has an AppleScript and a scriptable helper app. I'd like both the script and the helper app to end up accessible via -[NSBundle pathForAuxiliaryExectuble:].
Right now my AppleScript is in my main project, but I can't add it as a resource to my executable target. What is the "correct" way to do this in Xcode 3.1? If I change the File Type from "sourcecode.scpt" to something like "text", I can add it to my target, but it becomes a pain to edit.
Also, I would like to move the script to the subproject along with the helper app. Is it possible to do this, and have it show up as a product useable by the parent project?
I went to go add a build script to call 'osacompile', but found the "Compile AppleScripts" build phase instead. When I add that to my target, I am then able to add my script to it as well. For the record, I also found the still-undocumented OTHER_OSAFLAGS -x build setting to make the compiled scripts execute-only via http://www.noodlesoft.com/blog/2007/04/05/xcode-odds-ends-automated-builds/
It looks like the "Compile AppleScripts" phase puts the product into Resources/Scripts.
So it looks like it won't be practical to move my script to the same project as the scriptable helper app, but at least I figured out the first problem in a better way than I was hoping for.
hope this can help someone else,
-natevw |
_______________________________________________
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