runrevmark wrote:Hmmm - we'll see if we can get a script together that will extract SDKs from an Xcode DMG...
I downloaded the XCode 4.3.3 disk image, mounted it, and just looked inside the XCode.app package....
I copied that into the same location inside my installed XCode 4.6 installation in /Applications.
$ xcodebuild -showsdks
OS X SDKs:
Mac OS X 10.6 -sdk macosx10.6
Mac OS X 10.7 -sdk macosx10.7
OS X 10.8 -sdk macosx10.8
So it looks like it worked. Now to see if I can build from here...
I also had to go here and change a bit so it could find libstdc++:
and either rename the existing directory "i686-apple-darwin11" to "i686-apple-darwin11" or symlink it.
There was also a conflict with the build.h file in the engine and a system Build.h, so I renamed the livecode build.h to lcbuild.h and changed the files that referenced it.
I still had a few errors in here with cast/type conversions:
but now I am down to just 7 errors left...
Actually, just one:
ld: cannot link directly with /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.6.sdk/usr/lib/libssl.0.9.7.dylib for architecture i386
Not sure what to think about that, lipo says it has code for x86_64 i386 ppc7400 ....
Some notes on XCode 3.3 on Lion mentioned with this error string... http://stackoverflow.com/questions/1104 ... -correctly
But I was able to get around this by changing the dependencies from the version-specific (libssl-0.9.7.dylib) to just (libssl.dylib). Now just two more issues with it looking for the 10.5 SDK for android/iphone bits. Almost there!
But it doesn't launch yet...
Run from the console I see:
Startup error - /Users/n9yty/LiveCode/SOURCE/livecode/_build/mac/Release/LiveCode.app/Contents/MacOS/Toolset/home.rev
That file is not there, the Toolset dir isn't there at all. Coping it in from the ice directory allowed it to launch. Yay! But only when from Terminal in the LiveCode.app/Contents/MacOS directory... When launched via Finder or the open command it can't seem to find this Toolset directory. I'll have to look into it more, time for dinner.
That, and when I tried to run the solution I had been working on it doesn't see to have the XML stuff, or at least it hit an error trying to create an XML tree.