aboutsummaryrefslogtreecommitdiffstats
path: root/Library/Homebrew/cmd/--env.rb
AgeCommit message (Collapse)Author
2012-03-02Scupper sourceable output if brew install is pipedMax Howell
`brew install > file` should not give "export CC=/foo" output on Build Failures. Also moved the "Using clang" output to brew when BuildError is thrown as that is where it is interesting, and not if you just do `brew --env`.
2012-03-01Piped `brew --env` outputs in a sourceable formatMax Howell
So you can source `brew --env` to make it easier to build your own software, etc.
2012-02-21Don't hang if xcode-select -print-path is "/"Max Howell
Introducing MacOS.xctools_fucked?. Refs Homebrew/homebrew#10293.
2012-02-19brew --env: fix path to xcrunJack Nagel
Fixes Homebrew/homebrew#10327. Signed-off-by: Jack Nagel <jacknagel@gmail.com>
2012-02-17Find xcrun if user doesn't ever install Xcode 4.3 helper toolsMax Howell
2012-02-16Use xcrun; Ensure clang is the default compiler with Xcode 4.3Max Howell
Using xcrun as a proxy to execute the compiler tools is per its design. This means you can't treat ENV['CC'] as a path anymore, but I think I found the cases this was being expected and corrected them. It was not proper anyway to assume the variable was a path, it can be anything. Like a proxy. Like xcrun. Also more thoroughly clear ENV.
2011-12-31brew --env: respect --universalJack Nagel
Signed-off-by: Jack Nagel <jacknagel@gmail.com>
2011-12-16--env: dump a few more environment variablesJack Nagel
Signed-off-by: Jack Nagel <jacknagel@gmail.com>
2011-06-16Inclue HOMEBREW_USE_CLANG in --env outputAdam Vandenberg
2011-06-16Add clang compiler optionJosé Martínez
Signed-off-by: Adam Vandenberg <flangy@gmail.com>
2011-03-12Added --use-gcc flag.Stephen Allred
This allows you to use llvm as your default compiler and keep the cc symlink pointed at llvm, while allowing you to build forumla that requires the gcc. Signed-off-by: Adam Vandenberg <flangy@gmail.com>
2011-03-12Refactor the brew command into one file per commandMax Howell
The code was sucking. To the extent that maintenance was hard. It's a lot easier to work with code that is sensibly split at sensible boundaries. So now it is more like that. But the refactor is minimal. Because we don't want you to have more merge hell than absolutely necessary. If you merge you will need to pay attention to brew.h.rb (as it is deleted) and bin/brew (as command logic is gone). It will be painful, but you will just have to help git out by moving any changes around manually. Note compatibility.rb. It ensures that any function renames or removals don't break anything. We're pretty serious about backwards compatibility. And that's because we encourage you to hack around with the innards. And we couldn't do that if we would then just make stuff disappear behind your back.