Once both are installed you need to agree to the XCode licencing agreements, stipulating that Apple may call upon you to sacrifice your first born son as a test of your faith. This should really be the absolute first thing anyone does, since many things get linked to XCode's libs, so installing XCode later may mean reinstalling things later. You don't need to be part of the Apple Developer Program (which is $99 a year), but rumor has it that's about to change as Swift2 becomes more mature. To compile anything worthwhile, you need XCode and Command Line Developer tools, but before you can get that you'll need a Developer Account. Looking forward (well, not really) to see if this will break at the next system upgrade.Įveryone uses their computer differently (vim vs emacs!) and its no different on OSX, so this is really just my opinion: We ended up installing Xcode then homebrew (+ coreutils, wget.) and Anaconda for Python. Marking Chris Miller's answer as correct, although I used pieces of many answers, including some from Twitter. That plus the fact that I have personally little experience being in the driving seats of Macs. It seems that over the years package managers for Macs have gone in and out of fashion rapidly, thus I do not know which way to go.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |