Updated this morn… error in vs2008, not in 2010.
Removed the audio i/o module as … I should not have been including it anyway in our plugin, but letting you know anyway! 
- bram
Updated this morn… error in vs2008, not in 2010.
Removed the audio i/o module as … I should not have been including it anyway in our plugin, but letting you know anyway! 
Re-added module as I need some midi buffer things. Disabled all audio devices (as I don’t need them).
However now I’m getting a even more fun error:
PS: I know that release builds remove all these bits, but I suppose that for plugins most of the audio devices stuff should be disabled by default right?
Ah, thanks - should be ok now.
Yeah, that one is, these aren’t:
1>juce_audio_devices.obj : error LNK2019: unresolved external symbol __imp__UuidFromStringA@8 referenced in function "struct _GUID __cdecl juce::uuidFromString(char const *)" (?uuidFromString@juce@@YA?AU_GUID@@PBD@Z)
1>juce_RTAS_Wrapper.obj : error LNK2019: unresolved external symbol "void __stdcall juce::logAssertion(char const *,int)" (?logAssertion@juce@@YGXPBDH@Z) referenced in function "__int64 __stdcall juce::juce_InterlockedIncrement64<__int64>(__int64 volatile *)" (??$juce_InterlockedIncrement64@_J@juce@@YG_JPC_J@Z)
Ok, try again now.
Good news: KSDATAFORMAT_SUBTYPE_IEEE_FLOAT error is gone.
Bad news: I’m still getting these errors (one is RTAS related):
In debug:
juce_RTAS_Wrapper.obj : error LNK2019: unresolved external symbol "void __stdcall juce::logAssertion(char const *,int)" (?logAssertion@juce@@YGXPBDH@Z) referenced in function "__int64 __stdcall juce::juce_InterlockedIncrement64<__int64>(__int64 volatile *)" (??$juce_InterlockedIncrement64@_J@juce@@YG_JPC_J@Z)
In release: linker crashes @ link time!
If I should start a new thread regarding these let me know. This used to build just fine back in a07ce814eb7c8d5aa435f534755544ba102db132 (2012-12-18 18:06:01), but now I’m getting these. I guess I could start a bisect, but it’s gonna take me a while to get this figured out as each needs two rebuilds!
I reproduced the unresolved external with your JuceDemoPlugin (RTAS=on).
I’m not able to reproduce the linker crash with the demo plugin, but I’m still investigating.
Oh, it’ll just be because an RTAS build has to use a different calling convention - I need to give logAssertion an explicit JUCE_CALLTYPE declaration. Try now.
All problems solved, including the linker error (which was ours ours).
Thx!