Building a stand-alone AppleScript Studio application

Question

I’m taking a crack at building my first stand-alone application with AppleScript Studio. After many attempts to locate the needed “build” information in the various documentation resources I’m still pretty much poking around in the dark ...
My application runs fine in the Xcode IDE. No problems. The application that Xcode saves in the project’s Debug folder runs too, (well, on the computer I developed it on) even if I move it out of its folder ...
However, the app. doesn’t run on other macs. When double-clicked and it sorta fizzles without ever opening — wondering if the debug version relies on some resources within the project. I've installed it on a PowerBook and iBook, both running Mac OS 10.4
I tried Build/Release. This also produced an application (in the Build/Release folder) which when failing to launch and causes the OS to burp, “You cannot open the application “My First App” because it may be damaged or incomplete.” This app will not run on my development computer or other laptops (PowerBook and iBook.)
Build/Release also invoked three Xcode compiler error messages that seem to indicate that I need to change the NIB settings:
/usr/bin/ld: warning /Developer/SDKs/MacOSX10.3.9.sdk/System/Library/Frameworks/Cocoa.framework/Coco a cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (file not loaded)
/usr/bin/ld: warning /Developer/SDKs/MacOSX10.3.9.sdk/System/Library/Frameworks/AppleScriptKit.frame work/AppleScriptKit cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (file not loaded)
/usr/bin/ld: warning fat file: /usr/lib/gcc/i686-apple-darwin8/4.0.1/../../../libSystem.dylib does not contain an architecture that matches the specified -arch flag: i386 (file ignored)
Also got this warning(?):
/usr/bin/ld: Undefined symbols:
__keymgr_dwarf2_registersections
_cthread_initroutine
_atexit
_errno
_exit
mach_initroutine
_ASKInitialize
_NSApplicationMain
collect2: ld returned 1 exit status
Also tried Clean All. Same result.
I'm sure there's a simple step ... which I will remember well, 'cause I'm learning it the hard way.
John

Answer 1

However, the app. doesn’t run on other macs. When
double-clicked and it sorta fizzles without ever
opening — wondering if the debug version relies on
some resources within the project. I've installed it
on a PowerBook and iBook, both running Mac OS 10.4
You're right. You can't move a debug version of the app to another computer unless you copy the entire project folder. The debug version of the app requires access to other by-products of the build process in order to run.
Build/Release also invoked three Xcode compiler error
messages that seem to indicate that I need to change
the NIB settings:
The following errors are not related to your NIB file. They indicate you're trying to link against the 10.3.9 frameworks on an intel CPU. The 10.3.9 frameworks are PPC only.
/usr/bin/ld: warning
/Developer/SDKs/MacOSX10.3.9.sdk/System/Library/Framew
orks/Cocoa.framework/Cocoa cputype (18, architecture
ppc) does not match cputype (7) for specified -arch
flag: i386 (file not loaded)
/usr/bin/ld: warning
/Developer/SDKs/MacOSX10.3.9.sdk/System/Library/Framew
orks/AppleScriptKit.framework/AppleScriptKit cputype
(18, architecture ppc) does not match cputype (7) for
specified -arch flag: i386 (file not loaded)
/usr/bin/ld: warning fat file:
/usr/lib/gcc/i686-apple-darwin8/4.0.1/../../../libSyst
em.dylib does not contain an architecture that
matches the specified -arch flag: i386 (file
ignored)
[snip]
Take a look at the suggestions I made in this thread to make sure your project is set up to build a universal binary and to ensure that you're linking against the 10.4 universal frameworks.
Steve