> It's painless. > > You create an image in VMware Fusion and install on to it. I think I may > have even carbon copy cloned my 10.6.8 install and then just installed the > updates over it in VMWare Fusion. > > On Oct 18, 2014, at 1:16 PM, Bob Sabiston wrote: > >>> From: Igor Delovski <[email protected]> >>> Well, VMWare and 10.6 is the way to go. On my older MBA I even had a >>> non-server version running but now I forgot how I did it and since it's not >>> quite legal to do it, on my latest MBA I have 10.6 server in VMWare and >>> 3.2.6 works just fine. >>> >>> I have always worked with multiple windows floating around so in modern >>> Finder I have toolbars turned off and with some discipline and stubbornness >>> I can have separate windows in the latest Xcode for global search, >>> debugging, console and editing. >>> >>> Oh, and I even have SheepShaver in that virtual 10.6 so I can run ResEdit >>> when I need it. What's cooler than that? >> >> I tried the thing I mentioned earlier about clicking the executable, but it >> doesn’t work. It launches but trying to open the project gives errors, like >> the OP mentioned. >> >> Everyone’s talking about using VMWare to do this. Forgive my ignorance but >> Igor what do you mean about server/non-server versions? Is it harder to get >> a non-server version running virtually, and why wouldn’t it be legal? >> >> Also, does Parallels work as well for this? I don’t have VMWare. >> >> Thanks >> Bob
Is using a VM pretty much the only option for carbon apps now? Or can you still compile and run carbon apps under Yosemite using Xcode 6? I’ve been using 3.26 for years for this old carbon app, so I’m wondering what would be involved in getting it running in the new version of Xcode. Or maybe carbon is finally put out to pasture? Thanks Bob
_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to [email protected]
