The way xcode-select works is that Xcode installs some stub executables into /usr/bin that look for some other global file to see where the actual executables are. That could certainly be done for this but I wanted to keep it simple and avoid anything that required privilege escalation or global anything. I would rather try giving it the ability to automatically set the PATH and provide troubleshooting functionality (at least have it tell you if the right ghc is on the path, and if the right Xcode is installed).
I've never had any problems with homebrew. I use it to maintain a reference Haskell Platform installation. I love homebrew for other purposes. Many things have 'just worked' for me on homebrew that were a nuisance or impossible to install by hand or using other managers.
In the unlikely case that you are very experienced with Haskell and somewhat experienced with Linux but very new on the Mac platform, you can (after getting XCode or GCC) install Haskell for Mac (self-contained relocatable GHC builds). Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site. Haskell Platform − This is the best way to install Haskell because it will install the entire platform in your machine and that to from one specific location. This installer is not distributive like the above two installers.
I've always built multiple versions of GHC side-by-side under a custom path /usr/ghc, with /usr/ghc/now a symbolic link to my current work copy. I do this by script. I've used versions of this script to test new hardware; building 32 copies of GHC repeatedly in parallel literally caused a friend's very expensive but underspec'd compute server to curl smoke and shut down. I told him he should have let me help him built it himself, after ridiculing his vendor's choice of power supply. Standard installers make it very hard to manage side-by-side installs. Last I looked, any one-click GUI installer wove GHC into the Mac system, without even telling you where the pieces all go.
All too 1960's men-in-white-coats for me, I know people are just trying to help while accepting Apple cannon on 'correct' form, but I get privately distressed letting such an installer run on my system. Hence the scripting. This is very nice if there is a specific reason why you want a 'self-contained relocatable GHC build' that is bare-bones, or if you need the latest cutting-edge version of GHC. Thanks for doing this! But for a default 'Haskell for Mac OS X' for general use, I would recommend the Haskell Platform installer. Besides a fully automatic setup of GHC, you get a set of basic packages that all work together perfectly, all the paths set up in the way you would expect them to be on a Mac, and a simple uninstaller.
About the App • App name: Haskell Platform • App description: haskell-platform (App: Not Available) • App website: Install the App • Press Command+Space and type Terminal and press enter/return key. • Run in Terminal app: ruby -e '$(curl -fsSL /dev/null; brew install caskroom/cask/brew-cask 2> /dev/null and press enter/return key. If the screen prompts you to enter a password, please enter your Mac's user password to continue. When you type the password, it won't be displayed on screen, but the system would accept it. So just type your password and press ENTER/RETURN key.
The latest version of the Haskell Platform for Mac OS X is 8.4.3.Note that the current Haskell Platform is only compatible with OS X 10.8 and later. These packages are for Mac OS X systems not using a package manager.
Then wait for the command to finish. • Run: brew cask install haskell-platform Done! You can now use Haskell Platform.
0 kommentar(er)
