0
0

Hi,

I’m doing an application that requires some iPhone specifics introduced in 4.27.06 (simultaneous playback and recording without a pause on recordStart).

It ran beautifully until I upgraded to Snow Leopard and Xcode 3.2. Now the application only compiles and runs in the Simulator 3.1. If I try to compile to device with OS3.1, I get over a hundred error messages during linking, starting with this one:

[quote:1w7ig6p6]"_AudioSessionRemovePropertyListenerWithUserData", referenced from:
FMOD::OutputCoreAudio::close() in libfmodexL_iphoneos.a(fmod_output_coreaudio.o)
_AudioSessionRemovePropertyListenerWithUserData$non_lazy_ptr in libfmodexL_iphoneos.a(fmod_output_coreaudio.o)[/quote:1w7ig6p6]

Does anyone know if Apple changed something in Snow Leopard and/or Xcode 3.2 that broke FMOD’s compatibility?

btw I’ve downloaded and installed the latest FMODEx 4.27.09, but that didn’t help.

thx & brgds

  • You must to post comments
0
0

Can you make sure you are not accidentally linking with OS2.0 or some old version. We generally see that error when that is the case since the AudioSessionRemovePropertyListenerWithUserData was added in OS2.1.

There is no known compatibility issues with Snow Leopard and Xcode 3.2, that is what we build with here.

Do you have these problems with the examples?

  • You must to post comments
0
0

thx for the quick response Mathew,

I can compile and run any "non FMOD" app on the device, but when I try to compile and run any app using FMOD (the FMOD example apps included), they only work with the Simulator, but not the device, getting exactly the same linking errors as quoted above.

One more piece of info: in the build result window, I get the following warning messages just before the error message quoted in my first post:

[quote:3e1ikrkt]ld: warning: in /Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator3.0.sdk/System/Library/Frameworks/AudioToolbox.framework/AudioToolbox, file is not of required architecture
ld: warning: in /Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator3.0.sdk/System/Library/Frameworks/CoreData.framework/CoreData, file is not of required architecture
ld: warning: in /Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator3.0.sdk/System/Library/Frameworks/CoreFoundation.framework/CoreFoundation, file is not of required architecture
ld: warning: in /Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator3.0.sdk/System/Library/Frameworks/CoreGraphics.framework/CoreGraphics, file is not of required architecture
ld: warning: in /Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator3.0.sdk/System/Library/Frameworks/Foundation.framework/Foundation, file is not of required architecture
ld: warning: in /Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator3.0.sdk/System/Library/Frameworks/QuartzCore.framework/QuartzCore, file is not of required architecture
ld: warning: in /Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator3.0.sdk/System/Library/Frameworks/UIKit.framework/UIKit, file is not of required architecture[/quote:3e1ikrkt]

These are the frameworks I link to, except I don’t link to Simulator3.0.sdk, but to Simulator3.1.sdk, so why it’s looking for 3.0 beats me.

And yeah, I’m pretty sure I don’t link with OS2.0 anywhere.

Any ideas?

  • You must to post comments
0
0

Ooops, sorry. I was too quick there.

The FMOD example apps compile, link and run on the device too. So there seems to be something in my app’s Build settings. I’ll go through it and compare line by line.

  • You must to post comments
0
0

No problem, it looks like a simple config issue. I would suggest opening the Xcode project in a text editor to track down the references to 3.0 SDK.

  • You must to post comments
0
0

After having banged my head against the wall for days, I finally bit the bullet and created a new project from scratch and brought everything into it file by fle. It took me half a day, but at least now it works both in the simulator and device. A reference must have been screwed up somewhere.

thx for the support and brgds.

  • You must to post comments
Showing 5 results
Your Answer

Please first to submit.