On Mar 23, 2010, at 12:53 PM, ~suv wrote:
On 22/3/10 20:57, Stuart Edwards wrote:
On Mar 22, 2010, at 2:20 PM, ~suv wrote:
Stu - I don't understand why you don't have it with your Xcode installation. Hopefully Michael or JiHO will take a look at the ScriptExec xcodeproject if it needs to be updated for Snow Leopard. My knowledge about working with Xcode projects is close to zero and I do not have Snow Leopard installed.
sdk10.4 was an optional install that I didn't think I'd need. Now I have it.
Probably a(nother) dumb question - but how (and when) do I switch to gcc 4.0 ?
If I use the current script with sdk 10.4, will the result be useable on 10.6?
Can you give a short summary how you successfully built the app launcher (ScriptExec) on Snow Leopard [1]? Any changes necessary to the xcodeproject, once 'MacOSX10.4u.sdk' is installed?
~suv
[1] http://article.gmane.org/gmane.comp.graphics.inkscape.devel/33619
I'm actually embarrassed to report this but ............ In my continuing quest for instant gratification I took the app launcher out of my X11 package and dropped a copy of it into my 'broken' aqua package --- and it worked. The 'do not enter' sign disappeared from the app icon and it fires up as it should. It could be said that maybe the current performance problems relate in some way to this hack, but they are exactly the same as when I run the build from outside the bundle so I would conclude that they are not connected. Probably not ideal, but until we have a package script that calls for sdk10.6 it seems like an ok workaround.
Stu
Stu