Quickstart
- Install Xcode and the Xcode Command Line Tools
- Agree to Xcode license in Terminal:
sudo xcodebuild -license - Install MacPorts for your version of the Mac operating system:
Installing MacPorts
With Xcode, developers can open an existing iPad project and simply check a single box to automatically add fundamental Mac and windowing features, and adapt platform-unique elements like touch controls to keyboard and mouse — providing a huge head start on building a native Mac version of their app. Mac and iPad apps share the same project. This is INCORRECT. I am running the latest MacOS Catalina, and the full XCode is required: $ xcodebuild xcode-select: error: tool 'xcodebuild' requires Xcode, but.
MacPorts version 2.6.4 is available in various formats for download and installation (note, if you are upgrading to a new major release of macOS, see the migration info page):
- “pkg” installers for Big Sur, Catalina, Mojave, and High Sierra, for use with the macOS Installer. This is the simplest installation procedure that most users should follow after meeting the requirements listed below. Installers for legacy platforms Sierra, El Capitan, Yosemite, Mavericks, Mountain Lion, Lion, Snow Leopard, Leopard and Tiger are also available.
- In source form as either a tar.bz2 package or a tar.gz one for manual compilation, if you intend to customize your installation in any way.
- Git clone of the unpackaged sources, if you wish to follow MacPorts development.
- The selfupdate target of the port(1) command, for users who already have MacPorts installed and wish to upgrade to a newer release.
Checksums for our packaged downloads are contained in the corresponding checksums file.
The public key to verify the detached GPG signatures can be found under the attachments section on jmr's wiki page. (Direct Link).
Please note that in order to install and run MacPorts on macOS, your system must have installations of the following components:
- Apple's Xcode Developer Tools (version 12.2 or later for Big Sur, 11.3 or later for Catalina, 10.0 or later for Mojave, 9.0 or later for High Sierra, 8.0 or later for Sierra, 7.0 or later for El Capitan, 6.1 or later for Yosemite, 5.0.1 or later for Mavericks, 4.4 or later for Mountain Lion, 4.1 or later for Lion, 3.2 or later for Snow Leopard, or 3.1 or later for Leopard), found at the Apple Developer site, on your Mac operating system installation CDs/DVD, or in the Mac App Store. Using the latest available version that will run on your OS is highly recommended, except for Snow Leopard where the last free version, 3.2.6, is recommended.
Apple's Command Line Developer Tools can be installed on recent OS versions by running this command in the Terminal:
Older versions are found at the Apple Developer site, or they can be installed from within Xcode back to version 4. Users of Xcode 3 or earlier can install them by ensuring that the appropriate option(s) are selected at the time of Xcode's install ('UNIX Development', 'System Tools', 'Command Line Tools', or 'Command Line Support').
- Xcode 4 and later users need to first accept the Xcode EULA by either launching Xcode or running:
- (Optional) The X11 windowing environment for ports that depend on the functionality it provides to run. You have multiple choices for an X11 server:
- Install the xorg-server port from MacPorts (recommended).
- The XQuartz Project provides a complete X11 release for macOS including server and client libraries and applications. It has however not been updated since 2016.
- Apple's X11.app is provided by the “X11 User” package on older OS versions. It is always installed on Lion, and is an optional installation on your system CDs/DVD with previous OS versions.
macOS Package (.pkg) Installer
The easiest way to install MacPorts on a Mac is by downloading the pkg or dmg for Big Sur, Catalina, Mojave, High Sierra, Sierra, El Capitan, Yosemite, Mavericks, Mountain Lion, Lion, Snow Leopard, Leopard or Tiger and running the system's Installer by double-clicking on the pkg contained therein, following the on-screen instructions until completion.
This procedure will place a fully-functional and default MacPorts installation on your host system, ready for usage. If needed your shell configuration files will be adapted by the installer to include the necessary settings to run MacPorts and the programs it installs, but you may need to open a new shell for these changes to take effect.
The MacPorts “selfupdate” command will also be run for you by the installer to ensure you have our latest available release and the latest revisions to the “Portfiles” that contain the instructions employed in the building and installation of ports. After installation is done, it is recommended that you run this step manually on a regular basis to to keep your MacPorts system always current:
At this point you should be ready to enjoy MacPorts!
Type “man port” at the command line prompt and/or browse over to our Guide to find out more information about using MacPorts. Help is also available.
Source Installation
If on the other hand you decide to install MacPorts from source, there are still a couple of things you will need to do after downloading the tarball before you can start installing ports, namely compiling and installing MacPorts itself:
- “cd” into the directory where you downloaded the package and run “tar xjvf MacPorts-2.6.4.tar.bz2” or “tar xzvf MacPorts-2.6.4.tar.gz”, depending on whether you downloaded the bz2 tarball or the gz one, respectively.
- Build and install the recently unpacked sources:
- cd MacPorts-2.6.4
- ./configure && make && sudo make install
- cd ../
- rm -rf MacPorts-2.6.4*
These steps need to be perfomed from an administrator account, for which “sudo” will ask the password upon installation. This procedure will install a pristine MacPorts system and, if the optional steps are taken, remove the as of now unnecessary MacPorts-2.6.4 source directory and corresponding tarball.
To customize your installation you should read the output of “./configure --help | more” and pass the appropriate options for the settings you wish to tweak to the configuration script in the steps detailed above.
You will need to manually adapt your shell's environment to work with MacPorts and your chosen installation prefix (the value passed to configure's --prefix flag, defaulting to /opt/local):
- Add ${prefix}/bin and ${prefix}/sbin to the start of your PATH environment variable so that MacPorts-installed programs take precedence over system-provided programs of the same name.
- If a standard MANPATH environment variable already exists (that is, one that doesn't contain any empty components), add the ${prefix}/share/man path to it so that MacPorts-installed man pages are found by your shell.
- For Tiger and earlier only, add an appropriate X11 DISPLAY environment variable to run X11-dependent programs, as Leopard takes care of this requirement on its own.
Lastly, you need to synchronize your installation with the MacPorts rsync server:
Upon completion MacPorts will be ready to install ports!
It is recommended to run the above command on a regular basis to keep your installation current. Type “man port” at the command line prompt and/or browse over to our Guide to find out more information about using MacPorts. Help is also available.
Git Sources
If you are developer or a user with a taste for the bleeding edge and wish for the latest changes and feature additions, you may acquire the MacPorts sources through git. See the Guide section on installing from git.
Purpose-specific branches are also available at the https://github.com/macports/macports-base/branches url.
Alternatively, if you'd simply like to view the git repository without checking it out, you can do so via the GitHub web interface.
Selfupdate
If you already have MacPorts installed and have no restrictions to use the rsync networking protocol (tcp port 873 by default), the easiest way to upgrade to our latest available release, 2.6.4, is by using the selfupdate target of the port(1) command. This will both update your ports tree (by performing a sync operation) and rebuild your current installation if it's outdated, preserving your customizations, if any.
Other Platforms
Running on platforms other than macOS is not the main focus of The MacPorts Project, so remaining cross-platform is not an actively-pursued development goal. Nevertheless, it is not an actively-discouraged goal either and as a result some experimental support does exist for other POSIX-compliant platforms such as *BSD and GNU/Linux.
The full list of requirements to run MacPorts on these other platforms is as follows (we assume you have the basics such as GCC and X11):
- Tcl (8.4 or 8.5), with threads.
- mtree for directory hierarchy.
- rsync for syncing the ports.
- cURL for downloading distfiles.
- SQLite for the port registry.
- GNUstep (Base), for Foundation (optional, can be disabled via configure args).
- OpenSSL for signature verification, and optionally for checksums. libmd may be used instead for checksums.
Normally you must install from source or from an git checkout to run MacPorts on any of these platforms.
Help
Help on a wide variety of topics is also available in the project Guide and through our Trac portal should you run into any problems installing and/or using MacPorts. Of particular relevance are the installation & usage sections of the former and the FAQ section of the Wiki, where we keep track of questions frequently fielded on our mailing lists.
If any of these resources do not answer your questions or if you need any kind of extended support, there are many ways to contact us!
I wish I had known this when I first started because I delayed myself for 3 years before biting the bullet and buying a Mac.
Had I known about running Xcode on Windows or about the solutions below, I might’ve started building iPhone apps much earlier!
Rent a Mac
Before committing to buying a new Mac, you can actually “rent” one for development. You’ll remotely access the Mac and Xcode through your PC.
It’ll be like having the Mac desktop in a window on your Windows Desktop.
The really nice thing about this option is that the cost is really low and it’s the fastest option to get up and running.
If you decide that app development isn’t for you, you just cancel your plan.
1. MacStadium
These guys were featured in the recent Apple keynote when they introduced the updated Mac Mini! They have the newest Macs available.
(Use coupon code “CODEWITHCHRIS” for 50% off your first month. If you do, please let me know in the comments below. I’ll get a small kick back at no extra expense to you so thank you for supporting my site!)
If you go down this route for iOS app development, make sure you get my Xcode cheatsheet with references and keyboard shortcuts for Windows users.
There are a couple other companies that provide this service:
2. MacInCloud
This is the most well known service out of the three. You won’t have to install Xcode because it comes preinstalled. You can also do pay-as-you-go so it’s a pretty low commitment. Some people complain that it’s slow but you can try it out for yourself since it’s only about a buck an hour!
3. XcodeClub
XcodeClub is run by Daniel who is a passionate developer himself. From the reviews I see, the service is fast and friendly. The pricing is less flexible than MacInCloud and you’ll have to commit to at least a month.
Virtualize MacOS
If you’re a little more technically savvy, you can use virtualization software and run a “virtual Mac” on your PC.
The services above are essentially doing the same thing on their servers and then they charge you a fee to access the virtual machine.
By setting it up yourself on your own PC, you essentially cut the middle man out of the equation.
Unfortunately it does take a little bit of technical know-how to get this up and running.
The two most popular pieces of software to do virtualization are VirtualBox and VMWare Workstation.
You can download them below and then use Google to find a guide on how to install the latest MacOS (Mojave) with either VirtualBox or VMWare Workstation.
After that, spin up your new virtual Mac and download Xcode. This is as close as you’ll get to running actual Xcode on Windows!
4. VirtualBox
VirtualBox is open source software which means that it’s free. That probably explains why it’s a lot more popular than VMWare Workstation when it comes to running MacOS on your Windows machine!
5. VMWare Workstation
Unfortunately you’ll have to pay for this piece of software and at the time of this writing, a license costs about half the price of a brand new Mac Mini which is perfectly suitable for iOS app development. I would recommend you try VirtualBox first or try to buy a used Mac Mini.
Build a “Hackintosh”
You can also build a “Hackintosh” which is a PC that has been customized to run MacOS.
Xcode For Catalina
This requires the most effort out of all the options presented so far but it can work for someone who wants a separate physical computer running MacOS.
6. Hackintosh.com
A great resource for all things Hackintosh. The first How-To section contains links to a number of great tutorials for building your own Hackintosh and installing High Sierra.
7. Hackintosh Subreddit
I love looking for Reddit communities on anything that I’m interested in because there are always interesting conversations happening. Reddit provides a way to have a dialogue with like minded individuals, to get help and to help others!
8. Hackintosh Articles on 9to5mac.com
I included this link because it contains up to date news and articles for Hackintosh builds.
Third Party Solutions
Lastly, there are many third party solutions that you can use to do iOS development on Windows.
You won’t be using Xcode in these solutions but you’ll be able to generate an app that can run on iOS devices.
Xcode For Catalina 10.15.5
Check out these great Xcode alternatives:
9. React Native
Use JavaScript to build native mobile apps.
10. Xamarin
Use C# to build a mobile app that you can deploy natively to Android, iOS and Windows.
Xcode For Catalina 10.15.3
11. Appcelerator
Build native mobile apps using JavaScript.
12. PhoneGap
Build hybrid cross-platform mobile apps using HTML, CSS and JavaScript.