Xcode project fails in Release configuration, works in Debug configuration

[emendelson]

Something is wrong with the SheepShaver.xcodeproj file in the current version. The Debug configuration builds correctly, but the Release configuration fails with two errors.

I was able to fix this by deleting the Release configuration, duplicating the Debug configuration and naming the duplicated version "Release". I then checked the checkbox in the Build settings for the Release configuration that says "Strip Debug Symbols During Copy" as this seemed to be the only difference between the two configurations that I could find.

I tried making a diff file that would narrow down what was wrong, but it was far too big to be useful. But the problem with the Release configuration definitely exists.

(Tested under OS X 10.6, running in a VMWare emulated system.)

[vasi]

Is it the linking command that fails, unable to find the SDL framework? I got this because of something weird in my 10.6 SDK:

Etui:macemu vasi$ ls -l /Library/Xcode3/SDKs/MacOSX10.5.sdk/Library/Frameworks
lrwxr-xr-x  1 root  wheel  19 28 Oct 01:34 /Library/Xcode3/SDKs/MacOSX10.5.sdk/Library/Frameworks -> /Library/Frameworks
Etui:macemu vasi$ ls -l /Library/Xcode3/SDKs/MacOSX10.6.sdk/Library/Frameworks
total 8
lrwxr-xr-x  1 root  wheel   19 28 Oct 01:34 Frameworks -> /Library/Frameworks
drwxr-xr-x  3 root  wheel  102  4 Jan  2011 PluginManager.framework

It doesn't make any sense for there to be a Library/Frameworks/Frameworks! If I remove MacOSX10.6.sdk/Library/Frameworks, and replace it with a symlink to /Library/Frameworks, SheepShaver links correctly.

[emendelson]

On Nov 13, 2013, at 2:58 AM, Dave Vasilevsky notifications@github.com wrote:

Is it the linking command that fails, unable to find the SDL framework? I got this because of something weird in my 10.6 SDK:

Etui:macemu vasi$ ls -l /Library/Xcode3/SDKs/MacOSX10.5.sdk/Library/Frameworks
lrwxr-xr-x 1 root wheel 19 28 Oct 01:34 /Library/Xcode3/SDKs/MacOSX10.5.sdk/Library/Frameworks -> /Library/Frameworks
Etui:macemu vasi$ ls -l /Library/Xcode3/SDKs/MacOSX10.6.sdk/Library/Frameworks
total 8
lrwxr-xr-x 1 root wheel 19 28 Oct 01:34 Frameworks -> /Library/Frameworks
drwxr-xr-x 3 root wheel 102 4 Jan 2011 PluginManager.framework
It doesn't make any sense for there to be a Library/Frameworks/Frameworks! If I remove MacOSX10.6.sdk/Library/Frameworks, and replace it with a symlink to /Library/Frameworks, SheepShaver links correctly.

—
Reply to this email directly or view it on GitHub.

It’s been three months since I tried this, and I don’t remember the full details, but I think, yes, it was linking command that failed. Here are the few details that I posted at the time:

http://www.emaculation.com/forum/viewtopic.php?f=20&t=8109&start=31

Again, the debug setting built successfully; the release build didn’t.

[vasi]

Yeah,the debug build seems to be linking against the 10.5 sdk here, which has the correct Frameworks symlink.

[RonaldPR]

Ah, yes, I remember now. I bumped into this issue long time ago, changed the symlink, thought it was an anomaly in my setup only, and forgot all about it. I didn't think of it when emendelson reported the problem years later.

---

Op 13 november 2013, om 08:58, schreef Dave Vasilevsky notifications@github.com:

Is it the linking command that fails, unable to find the SDL framework? I got this because of something weird in my 10.6 SDK:

Etui:macemu vasi$ ls -l /Library/Xcode3/SDKs/MacOSX10.5.sdk/Library/Frameworks
lrwxr-xr-x 1 root wheel 19 28 Oct 01:34 /Library/Xcode3/SDKs/MacOSX10.5.sdk/Library/Frameworks -> /Library/Frameworks
Etui:macemu vasi$ ls -l /Library/Xcode3/SDKs/MacOSX10.6.sdk/Library/Frameworks
total 8
lrwxr-xr-x 1 root wheel 19 28 Oct 01:34 Frameworks -> /Library/Frameworks
drwxr-xr-x 3 root wheel 102 4 Jan 2011 PluginManager.framework
It doesn't make any sense for there to be a Library/Frameworks/Frameworks! If I remove MacOSX10.6.sdk/Library/Frameworks, and replace it with a symlink to /Library/Frameworks, SheepShaver links correctly.

—
Reply to this email directly or view it on GitHub.