Quote:
Originally Posted by Lostz
How to set a Windows REAPER_DIR/REAPER64_DIR?
|
These are "environment variables", they must point to the path where REAPER 32-bit resides (or REAPER 64-bit, respectively). On Windows, they are required to build SWS. To define them see:
http://www.itechtalk.com/thread3595.html. On OS X, those vars are optional. On Marvericks, I had to add them in /etc/launchd.conf (which isn't POSIX compliant, I think...)
Anyway, as a bonus on both OS's, when those env. vars REAPER_DIR and REAPER64_DIR are defined, REAPER v4.72+ will also generate the up-to-date API functions header (reaper_plugin_functions.h) where it should, by default -- good to know for all extension plugins, not only SWS
Quote:
Originally Posted by vtsaran
Hi,
It is increasingly impossible to maintain both Xcode 3.x and 5.1 on the same Mac OS any more. When I attempt to compile SWS extension with 5.1, I naturally get a lot of errors.
What are the major differences here to prevent SWS from compiling in Xcode 5.1?
|
Hard to tell w/o the exact error messages...
On top of my head, the most probable reason is that XCode5 doesn't come with all needed OS X SDKs (down to 10.5).
If you do not plan to contribute the SWS open source, but just mess around, you can probably workaround this in the XCode project properties: just define a higher Base SDK and Deployment target.
If you want to fix things properly, and since you already have XCode3 installed, you can probably share the needed SDKs thanks to a trick like:
http://stackoverflow.com/questions/5...ort-to-xcode-4 (for XCode4, but should work for 5 too).
Personally, I've never used XCode3. I'm using XCode 5.0.2 and everything compiles smoothly out of the box (using the SWS XCode 3.1 project, I mean). I just had to install all missing SDKs via
http://devernay.free.fr/hacks/xcodelegacy/ (<- this link saved my butt!!)
Then, the only thing I had to tweak is: project properties > LLVM 5.0 Objective C > Implicitly Link Objective-C Runtime Support, set this to "No".
HTH!