OSX build script doesn't check presence of Cg framework before installing.

[juj]

The implementation of the Cg download in #380 ( https://github.com/Adminotech/tundra/commit/e6294e5341b2b4b13fc8aa790cd9b25c92a5aff7 ) generates an installation to the user directory, but the test of its presence is done based on a manually touched tag file.

This makes hosting multiple separate instanced of Tundra on an OSX system impossible, since the subsequent installations will overwrite each other, until they both have generated their own tag files.

also, on my system the build script doesn't have access permissions to write to /Users/lc/Library/Frameworks , to which I've already manually deployed Cg. This causes the script to fail, not understanding that it shouldn't try to install Cg.

The OSX script should be adapted to check the presence of Cg framework directly, instead of checking based on a tag file.

[juj]

see e.g. this failure http://clb.demon.fi:8114/builders/osx-Tundra/builds/17/steps/Build%20Tundra/logs/stdio

[juj]

Thanks for the quick work on this!

Testing on the build bot, I'm getting the same error on Ogre:

http://clb.demon.fi:8114/builders/osx-Tundra-incoming/builds/21/steps/Build%20Tundra/logs/stdio

it is trying to place the built Ogre into /Users/lc/Library/Frameworks/Ogre.framework.

Can it be placed into depsdir as well?

[cvetan5]

Yes. Still, Ogre.framework is needed on runtime to be in one of the system framework paths (that is, to avoid setting DYLD_FRAMEWORK_PATH env before running Tundra in order to find frameworks in paths elsewhere) which are

• /System/Library/Frameworks
• /Library/Frameworks
• ~/Library/Frameworks etc.

so I should make a custom script to be run with elevated privileges to take care of that.