Just to save someone 3-5 minutes of time, if you install the 10.4u SDK to target Tiger machines with Xcode 3.2 (Snow Leopard), you will have to change a build setting to get Xcode to compile.
In the settings for your target, change the compiler option from “System Default – GCC 4.2″ to “GCC 4.0″. Then the error message will go away and you can build for Tiger.
@Markus
Sounds like everything is in place, but I’m not familiar with AppleScript Studio.
However, I did have a lot of trouble with an AppleScript on Tiger and Snow Leopard both, which I wrote a few years ago. I struggled getting it to run on Snow Leopard, and eventually got it working flawless by checking the “Open in 32-bit mode” from the Get Info window. I can’t remember if that was before or after I had made a small edit to the script.
It was very flaky on Tiger after that as well, as I shared it with a colleague. And I was also trying to whip up an Automator workflow, which would not run on Tiger after I was finished. Not sure if I used an action that wasn’t available on Tiger or if Tiger just won’t run newer Automator workflows.
Let us know if you do get it working and what steps you had to take to get it there.
For the records: I solved this issue by setting up two different targets.
More information on the Apple Script Studio mailing list here:
http://lists.apple.com/archives/AppleScript-Studio/2009/Sep/msg00083.html
Submitting Your Comment, give me a second...
However, it won’t compile if you build it as a 64-bit Universal. It has to be 32-bit Universal