Update SheepShaverLauncher for modern XCode and OS X #25
Conversation
The previous Mac SDK setting, 10.4, is very old and does not allow compilation on recent versions of OS X. Same with the compiler, gcc 4.0. Since SheepShaver doesn't purposefully target a specific SDK or compiler, it's better to just use XCode's default, which should always be usable. If a user wants a specific SDK, they can set it themselves.
On Mac OS X 10.6, many informal protocols have become formal, and failure to declare conformance to them is an error. Declare our delegates and data sources to be conformant, conditional on an SDK >= 10.6
|
Can you split the source file changes and the project file change? I'm reluctant to take the proj file change, since I'd like to keep the project able to produce binaries that work on 10.4. |
|
Thanks for the quick reply. I agree that we shouldn't specify an SDK of 10.6 or something. I just think it's better to specify no SDK at all (and let XCode select its default) instead of specifying an SDK that may not exist. In any case, if you really just want the source file change, it's already in a separate commit. You should be able to 'git fetch' from my repo and then 'git cherry-pick' the second commit "Compile on 10.6+ SDK", which still leaves 10.4 as the default SDK. |
|
While we're at it, it would be great if SheepShaverLauncher's add disk dialog allowed the selection of sparsebundles. We could just set |
|
Isn't that to allow open and save dialogs to have access to files inside .sheepvm virtual machine packages? Op 4 april 2013, om 16:04, schreef Dave Vasilevsky notifications@github.com: While we're at it, it would be great if SheepShaverLauncher's add disk dialog allowed the selection of sparsebundles. We could just set [open setCanChooseDirectories:YES]. But I'm not sure why we treat bundles as directories in the first place. Is there a reason for the [open setTreatsFilePackagesAsDirectories:YES] call? — |
|
Oh, I never considered that anyone might do that! Ok, in that case I guess the best thing to do is use setCanChooseDirectories:YES. It's a little weird to expose the internals of sparsebundles, but I can't think of anything better. |
|
That is how you manage (choose, add, create, remove) the files inside the virtual machine, either with the Launcher or with the SheepShaver built-in prefs editor, regardless whether the VM is a folder or a .sheepvm bundle. Op 4 april 2013, om 16:34, schreef Dave Vasilevsky notifications@github.com:
|
Users should be able to select sparsebundles in the disk prefs, but should still be able to navigate inside .sheepvm bundles. See cebix#25 (comment)
Users should be able to select sparsebundles in the disk prefs, but should still be able to navigate inside .sheepvm bundles. See cebix/macemu#25 (comment)
|
Super out of date |
Minor fixes to allow SheepShaverLauncher to compile out-of-the--box on the 10.6 SDK and XCode 4.x. I don't anticipate the changes breaking earlier versions, though I have not been able to test.