Recently i upgraded to mountain lion.I want to open my old projects in older version of xcode 4.3 and i don't want to use xcode 5 for some reason.
Is there any way to open xcode 4.3 only. I have installation file of xcode 4.3 if its needed to reinstall.
It gives alert "This installation of Xcode 4.3.2 requires Mac OS X 10.7 Lion."
I know how to run my projects in other versions with old simulators... but only need 4.3
Any Suggestions?
Ignore the snarky comments by people like matheszabi; there are good reasons to support the millions of units of older devices. Tip: If you are looking at picking up older devices, you'll want to target iOS 4.2.1 not 4.3, as every device supporting 4.3 can be upgraded to iOS 5. See Highest Version of iOS Supported.
Virtualizer
To answer your question, "Any suggestions?": Use a virtualizer like Parallels, Fusion, or VirtualBox to run Lion, Mountain Lion, or Mavericks in a virtual environment. This arrangement has many advantages, including resisting the pushing and shoving of Apple to constantly upgrade our OS, Xcode, and iOS targets.
Another advantage is a pristine working environment with its own clean Keychain, Desktop, and so forth having only items related to Xcode project(s). All my own personal stuff is kept to the real Mac. I think of the real Mac like I do my home, with personal property, while I think of the virtual Mac as my office space, my cubicle, having only work-related items.
The one thing you'll need is memory (RAM). If you want a 3 or 4 gig virtual Mac, you'll need about that much space unused on your Mac. By unused, I mean the green colored piece of pie in Activity Monitor.
My Experience
For my current project, I run Xcode 4.6.3 targeting iOS 5 & 6 in Parallels 8 (9 is now available) on a Mac mini (Late 2012) with 16 gigs of memory and i7 quad-core with 8 virtual cores driven by Mountain Lion 10.8.5 on the real Mac, while the virtual Mac has 4 gigs of memory and 2 cores. For the most part this works very well. A few bugs, but no show-stoppers.
The only bad bug is that copying text from the real Mac and pasting into the virtual Mac appends an extra mysterious invisible character that wreaks havoc, including preventing compiling of Objective-C code. I routinely do searches for that evil character, and try to make a habit of hitting Backspace after pasting text brought over from the real Mac.
Another bug: Horizontal scrolling by finger-swiping on my Apple Magic Mouse does not work in the virtual environment.
But Parallels 8 + Mountain Lion + Xcode 4.6.3 works well. You can plug in an iOS device for direct debugging via USB cable – Parallels asks whether you want the connected device to be seen by the real Mac or the virtual Mac.
I've also run earlier versions of Xcode 4 on Lion (besides Mountain Lion) in Parallels 8.
With this arrangement, I am free to consider upgrading my real Mac to Mavericks while keeping my Parallels 8 + Mountain Lion + Xcode 4.6.3 work environment intact. Though, I may need to shell out some money to upgrade my Parallels 8 to the new version 9. No such thing as a free lunch! (But this arrangement comes close)
Backups
Tell Time Machine to avoid backing up the 20-50 gig file that is your virtual Mac's hard disk. Instead, do an occasional backup of that large file. More often, make a backup of your import work files and Xcode project, copying off to Dropbox, Google Drive, or external hard drive or SD card. If that file that is your virtual Mac's hard disk ever gets corrupted, you may lose everything. So backup religiously – though I'm sure you do so anyways now. ;-)
Looks like Xcode 4.3 doesn't know about Mountain Lion, the fix would be downloading and installing Xcode 4.6.2 from developer center, which surely supports it.
Related
I actually built a Hackintosh to learn programming with Xcode. It runs on my Asus X555LA laptop. I downloaded the latest Xcode 9 GM build from the Apple Site (not from App store). After extracting, when I tried to install, it shows "You can't use this version of the application "Xcode" with this version of macOS; You have macOS 10.12. The application requires macOS 10.12.6 or later".
Is there any tweak to make it run on my Sierra 10.12 itself? I can't really think about upgrading the macOS version as it's a Hackintosh. I followed this guide to install macOS on my Asus laptop.
Xcode requires latest macOS, you have no choice, you need to upgrade the macOS version on your Hackintosh. Or better: Reinstall macOS in a recommended way on your PC, if you're doing Hackintosh... :)
The guide you linked is very poor... Never use premade install images, because these have been modified in an uncertain way, and you don't want to install a premade undocumented mess to your computer. It might be packed with threats, malwares, spy tools and so on.. It's the worst thing I can imagine in security aspect to install an OS image from uncertain source.
Also, there is no universal macOS installer for PCs - even though many are trying to find a way to create it: it's a bad idea and it will never succeed because there are so many PC parts, millions of differently built computers..
The only way to create a stable fully functional Hackintosh is to know your hardware and create an installer flash drive for that specific PC. First you have to download the latest macOS Sierra from AppStore, this is the only source that you can trust, because it's downloading from Apple's servers. Then install a small program, called Clover bootloader to the flash drive to make it bootable.
This is the only full and up to date guide for PC laptops. If you have questions, register to the linked site and start a new forum thread posting your questions. They will help you but please read this guide at least 3-4 times carefully because everything is described here.
after reading the apple SDK guide
https://developer.apple.com/library/mac/#documentation/developertools/conceptual/cross_development/Overview/overview.html
I'm still confused of how to make the mac app backward compatible & how to test them properly
I have an app, I run it and tested it on Mountain Lion 10.8 without any problem, however I want to make this app backward compatible so that other users can run it on a mac 10.6 - 10.7 machine.
I have an apple developer id and I can download the old versions of 10.7 and 10.6, but the problem is, I have a 2011 macbook air which is currently running 10.8, and that's the only apple machine that I have. Can I test the 10.7 and 10.6 by using vmware or parallels?
in my project settings, I set the target deployment to 10.6 (as I want 10.6 users to run my app), but should I set my SDK to 10.8 or 10.7? if I set the SDK to 10.8 but having the target deployment set to 10.6, if I fix all the xcode warnings will it run successfully on 10.6??
from the SDK drop down, I can only set to 10.8 or 10.7, but 10.6 is missing, how do I fix that?
thanks in advance
I develop on a 10.8 box and support back to 10.5. Just a couple of months ago we dropped 10.4 PPC support, and I'm still cleaning out some of the 10.2-specific code. This may get a little rant-y, but I've been doing old versions for a long time. I have some opinions on the matter.
No matter what Apple says in their docs, if you want to support 10.6, then build with the 10.6 SDK. Do not rely on distribution target.
I have had this discussion with the Xcode engineers, and while they hold to Apple's party line that you should always build with the latest SDK, they also acknowledge that it's generally insane to do so. If you build against the 10.8 SDK and mark your deployment target at 10.6, you will get no warnings for using methods that do not exist on 10.6. The only way you will discover that you've used a nonexistent method is that it might give you strange bugs when run on 10.6. That's insane.
Remember, OS X doesn't crash when you send an unknown selector. It just aborts the current runloop. So the bugs are even harder to track down then on iOS, where it crashes the app.
Sure, you can do weak linking. Talk about dangerous.... Yes, there are a few times this is useful, but the compiler gives you no warning if you don't do it correctly. If I'm going to do weak linking like this, I go the other way, linking against the old SDK and copying the new function's prototype into my implementation. That way I have documentation of every function I think I'm going to weak-link.
Download the old SDKs and symlink them into your Xcode distribution.
Guard them jealously. Apple will try to delete them every time you upgrade Xcode. Make your own copies and stick them in /SDKs or somewhere else away from Xcode. I provide a script called fix-xcode to manage the symlinks automatically. Am I bitter at Apple for their relentless insistance on deleting my old SDKs? Yes, I am.
You can run 10.6 Server in a VM legally. You can run 10.7+ Desktop in a VM legally. These are good ways to test your code.
Or you can do what I do and have a small pile of old MacBooks each with two or three partitions on them that you reboot all the time.
Now that 10.7 comes from App Store, it's a little harder to make VMs. My strong recommendation is to snapshot your image immediately after install, and make a clean backup copy of it. You'll want to be able to clone that image from time to time when you need to get back to a "raw" machine.
Get in the habit of squirreling away SDKs as they come out. 10.8 will be old some day. You might as well make a copy now while it's easy.
Whether you support individual dot-releases or not, it can be very helpful to keep around the upgrade packages for individual dot releases. When you encounter customers running non-current releases, it's nice to be able to check whether an "unreproducible" bug in fact is easily reproducible on their specific version. Whether this is worth it or not depends heavily on your product and customers. It was a life-saver for me when 10.4.11 made major changes to WebKit during a dot release...
Invest in a small NAS or a big external USB drive (though I've had trouble with those failing when used extensively, so I prefer a RAID). You'll need the space. You want to hold onto lots of VMs and lots of SDKs and sometimes even old versions of Xcode.
Adding to Rob Napier's great in-depth answer:
To use an old SDK, put the SDK (or a symlink) to it here:
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs
With XCode 7.3 or later, you need you to open this file and change "MinimumSDKVersion" (otherwise XCode will refuse to use the old SDK):
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Info.plist
You can install multiple versions of Mac OS on a single machine, booting between each.
The SDK should be the latest (10.8).
See 2.
One alternative to 1 that I've considered (I am in the same boat) is to create a Snow Leopard Hackintosh using an old PC and just installing Lion and Mountain Lion on my MBP.
You need to do these settings :
1.Set the Base SDK to Current version of Mac (ex. 10.7)
2.Set the Deployment SDK to older version (ex.1.4)
I recently updated my MacBook Pro (2.3 GHz Intel Core i5) from Lion to Mountain Lion and simultaneously upgraded Xcode to the latest 4.5 version. I've experienced one very irritating problem. While programming I'm used to have a couple of tabs opened at a time. Ever since I updated, each time I switch tabs, Xcode freezes up for a bit (a couple of seconds). Does anyone have a suggestion to solve this problem?
I followed a tip on deleting project.xcworkspace to improve performance. Which seamed to help, but only for a short period of time.
It's a common issue and was fixed in XCode 4.5.1.
https://devforums.apple.com/thread/167765?tstart=0
If you have multiple partitions (maybe a backup of Lion was kept) ensure that xcode really comes from the Mountain Lion partition.
The App Store App update for Xcode seems to take the first Xcode.app it finds and will apply any update to that version. In my case it updated the (inactive) Lion partition, even so I booted from the ML partition.
xcode-select did not complain when I tried to change it to the ML version.
So I ended up doing the great housekeeping:
do a chmod 000 /Volume/<old Lion partition>/Applications/Xcode.app
installed a fresh copy on Xcode.app into /Applications
verify the destination of the dock icon (must point to the ML Xcode.app)
My Xcode is now fast as before and it remains fast. You can get the Xcode dmg and the command line tools from https://developer.apple.com/downloads/index.action. I don't think there is a difference in the binaries, but with the DMG I could see where I dropped the Xcode.app.
I found your question before I discovered a partial solution.
As of today, I find XCode 4.6.1 GUI dog slow for my taste, specially considering that I run on a one year old mac, SSD, compile to a 2GB RAM disk and still have 6GB RAM left. Even Eclipse runs lightning fast compared to XCode
4.5.1 did improve something, but after a long time using XCode I do not have any hope for some of its problems being solved ever.
That being said, I have noticed that "Live issues", the main tool bar and all the panels slow down tab switching to same degree. The biggest offender so far are the navigator panels.
Once I got used to a minimalistic Xcode window, layout some specific task tabs, keep a separate window for xibs and learned the shortcuts to enable/disable the panels, I no longer suffer so much with XCode responsiveness, but there is still some lag that can be clearly felt.
Check that there is not heavy coding on ViewWillDisappear.
Also if you have NSURLConnection or any other having delegate methods should not get called while switching tabs.
I have just bought a macbook air 11" with Lion 10.7. I installed xcode 3.2.5 on it. But its not working. Xcode is installed, consuming much space but I cannot see it in applications. Somewhere I heard that xcode 3 will not work on Lion 10.7, only xcode 4 is compatible on this os. Is it really true? I tried removing xcode 3 but efforts go worthless. What should I do to uninstall it?
For Xcode, you want to use scripts provided with Xcode to remove it completely. Open a terminal window and invoke /Developer/Library/uninstall-devtools. Alternatively, you can just drag the Developer folder to the trash, but I don't think that removes everything that gets installed by the installer.
And no, Xcode3.2 won't work (entirely right) under Lion. You need Xcode4, v4.2 being the most recent with the iOS5 SDK. And if you want to submit anything to Apple, you'll need 4.2 (i.e. the latest released tools) anyway, at this point.
I would use this utility. It's always worked better than the traditional way to "unistall" applications form OSX
http://appzapper.com/
The reviews have always been good for this app.
I want to Install any smooth working version of XCODE(for Iphone Apps development) on MAC machine having configuration as follows:-
MAC OS Z1-9.2.2,
Built In RAM-128 MB,
MAC OS ROM 9.0.1.
What are the feasibilities with that MAC.
Please help as I am just One day old for MAC.
No, it's not possible. It requires a modern Mac OS X. Xcode4 requires at least Snow Leopoard, and IIRC so does the current Xcode 3.2.x.
Even if it were possible, my Xcode4 right now occupies about 590MB of RAM at the moment of this writing. You wouldn't want to run something like that on a system with just 128MB RAM.