That sounds nasty. I’ve not got leopard yet - are you using the new xcode 3?
Also, an option to install/upgrade the 10.2 sdk is no longer available on the DVD (at least I could not find it). In fact, the 10.2 sdk folder was removed when doing an upgrade install on my system. So now, JUCE no longer builds (with default build settings) on my system. It built fine before the upgrade.
Ben
Yes, I tried a build with the latest SDK 10.5 and the only things I had to change was some common types e.g. uint8-> juce::uint8’s etc, that sort of thing…
Sadly I never got to ACTUALLY test everything in anger as the last time it crashed I had to totally re-install the OSX from scratch!
I’m about to try again, with all the sources on my (rebuilt) Mac - I’ll report back
{BTW- Symptoms: Hang- CC can’t be killed, shutting down OSX fails (presumably because CC won’t die) - So powering off must leave the filesystem in some horrid state
Following this OSX kept booting and going into OSX Setup app - there are ways around it, but as all the important stuff was backed up- and I only had to re-install from DVDs, so it hasn’t been too bad - Still, puts me back a few days 
}
What can have they done to CC that makes it unkillable?? Must be a device driver that it’s using going mad… Hmm. I might wait a while before I upgrade!
It might be the process killer/logout/shutdown that’re the problem, too - Just before I updated to the (very) latest Plogue Bidule, I had re-installed the previous release (which had been running fine under Tiger), and I deleted an Audio IO bidule (plugin), and the same thing happened - I couldn’t kill it, the processor list showed it as not responding, but worst of all, I couldn’t Shutdown or log out (both operations timed-out waiting) leaving me no option but to reboot by powering down again… Sheesh!
Since then, I’ve run it successfully (and built my plugin both under 10.4 and 10.5 SDK successfully) and run them under (the latest) Plogue Bidule (haven’t tried the demo host yet), so it’s rather hit and miss. Hopefully someone in California will receive my regular XCode dump-logs and spot the problem (I haven’t tried looking to see if others have had similar problems - if anyone spots it, please let me know, ta)
I hope I’m not taking this too far off topic, but I’m having trouble doing a ppc build with Leopard and Xcode 3. i386 alone builds and runs the Juce demo just fine with the 10.4 SDK, but adding ppc gives me this link error:
I’m no Mac expert, but it seems that libTIFF (which points to /usr/local/lib/libTIFF.3.7.4.dylib) doesn’t include a ppc build. What can I do about this?
I don’t know if this is of any help, but I had to change juce.xcconfig to:
ARCHS = ppc i386
// For 10.2 compatibility, use these values:
//GCC_VERSION_ppc = 3.3
//MACOSX_DEPLOYMENT_TARGET_ppc = 10.2
//OTHER_LD_FLAGS_ppc = /Developer/SDKs/MacOSX10.2.8.sdk/usr/lib/gcc/darwin/3.3/libstdc++.a
//SDKROOT_ppc = /Developer/SDKs/MacOSX10.2.8.sdk
// For 10.3 compatibility, use these:
//MACOSX_DEPLOYMENT_TARGET_ppc = 10.3
//SDKROOT = /Developer/SDKs/MacOSX10.4u.sdk
//SDKROOT_ppc = /Developer/SDKs/MacOSX10.3.9.sdk
// For 10.4 compatibility, use these:
MACOSX_DEPLOYMENT_TARGET_ppc = 10.4
SDKROOT = /Developer/SDKs/MacOSX10.4u.sdk
SDKROOT_ppc = /Developer/SDKs/MacOSX10.4u.sdkoops
Apparently I had a bunch of libs in /usr/local/lib, and for whatever reason Xcode was trying to link those in, despite JUCE never actually using them. I was seriously thinking about wiping everything clean and starting from scratch for Leopard before this problem, so I ended up doing that, and now it builds fine (after modifying the ppc flags, of course).
Interestingly enough, the reformat also seems to have made Code Sense start working again with JUCE, which it hasn’t done for quite a while. I must have had something very funky going on with Xcode, but I generally just use it for building so I hadn’t really noticed.