Do you mean working as in compiling, or working as in loading and actually debugging in PT?
I’m very keen to avoid having more than one project, have managed for quite some years building everything from a single code base and I don’t want Juce to change that 
Kind regards
Dave
I mean working as in compiling.
I still build everything from the same code base, but I have multiple projects. Right now, I have 3 projects for OSX for ValhallaRoom (VST, AU32/RTAS, AU64). Theoretically, I could combine the AU builds, but there are things I need to exclude for the 64-bit AU (Carbon files), and it is easy enough to maintain the 3 projects. I also try to keep things running for PPC on 10.4, as well as Intel, so this adds to the complexity.
For Windows, I have 2 projects for ValhallaShimmer - 32/64 bit VST, and RTAS. The fact that the PT SDK is built in VS2005 throws a kink into the process.
Sean Costello
Did you set all that up with the “Introjucer” as it is now known? I don’t mind having two projects in the same solution that handle the VST and RTAS builds, but I don’t see how that could be done except for manually.
Cheers
Dave
BTW there isn’t a problem building the PT SDK with VC2008, I’ve done it here with PT_73 and PT_80. Haven’t tried with VC2010 but I’m sure it can be done.
Sorry, I missed this line hence the edit. Does that mean then that you have never been able to get a debug RTAS build to compile using the Juce wrapper? is that against PT_73_SDK or PT_80_SDK? I have no problems with my own wrapper and PT_73_SDK.
