homebrew - :beer: The missing package manager for OS X.

Age	Commit message (Collapse)	Author
2014-06-03	Rewrite xcrun wrapper in shell	Jack Nagel

2014-05-08	Always use stub tools in /usr/bin on 10.9	Jack Nagel

2014-04-29	xcrun wrapper: rephrase comments	Jack Nagel

2014-04-29	xcrun wrapper: reorganize so we only access ARGV once	Jack Nagel

2014-04-29	xcrun wrapper: inline try method	Jack Nagel

2014-04-29	xcrun wrapper: skip superenv bin when walking PATH	Jack Nagel

2014-04-21	Print the attempted command when xcrun wrapper fails	Jack Nagel

2014-04-21	Use File::PATH_SEPARATOR since we use it everywhere else	Jack Nagel

2014-04-20	Delay loading Pathname until we absolutely need it	Jack Nagel

2014-04-20	Use a multiline conditional to make this code more readable	Jack Nagel

2014-04-20	Stop loading a bunch of monkeypatches every time xcrun is invoked	Jack Nagel

2014-04-20	Use File.expand_path	Jack Nagel

2014-04-20	Remove obsolete DEVELOPER_DIR hacks	Jack Nagel
	These days Homebrew refuses to do anything if the xcode-select path is busted, so this workaround is unnecessary.
2013-11-21	Remove some monkeypatches	Jack Nagel

2013-09-25	Silence xcrun output in wrapper	Misty De Meo
	Our wrapper always runs the real xcrun at least once, to try to find the path of the tool being run, but this meant that we were generating a huge number of error messages on every cc invocaton. Mostly this was annoying but harmless, but notably it managed to break the compilation of go.
2013-06-03	superenv: Work if build tool changes DEVELOPER_DIR	Samuel John
	Some build systems still set the DEVELOPER_DIR to /Developer and then nothing works any more (xcrun, xcodebuild etc.) I am looking at you MacVim.
2013-06-02	superenv: find Homebrew's gcc-4.2	Misty De Meo
	If we're using a homebrewed gcc-4.2, xcrun may fail to find it (or, worse, find superenv's shim instead). Explicitly add it to the PATH and search all path elements for the requested tool. Also make sure to specify 'gcc-4.2' as the compiler name, not plain 'gcc'. That can resolve to llvm-gcc and to gcc-4.0 on various Xcodes.
2013-03-21	Better superenv support for Xcode elsewhere	Samuel John
	- The Library/ENV/4.3/xcrun shim now respects ENV['DEVELOPER_DIR'] instead assuming the location of /Applications/Xcode.app/Contents/Developer. - The env var DEVELOPER_DIR is set if it is not already. So, during superenv this var is always set and we no longer have to care about people with unset or wrongly set xcode-select stuff. This has been a major PITA in the past. - determine_developer_dir (which is used to set the DEVELOPER_DIR var) now uses MacOS::Xcode.prefix which is proven and very capable and uses splotlight correctly. - Replace (and remove) MacSystem.xcode43_developer_dir with Xcode.prefix Closes #18618
2013-02-05	xcrun: remove suggestion that doesn't work	Adam Vandenberg
	Closes #17443.
2013-01-26	xcrun: actually try fallbacks	Misty De Meo
	xcrun has a lot of fallbacks if the first case fails but never actually reaches them on CLT systems since it doesn't check the validity of the first path before executing it. (When should it reach these? Mainly for non-Xcode compilers we support, e.g. apple-gcc42 which can be found by xcrun but which isn't in /usr/bin) The xcrun invocation also needed chomping.
2012-09-29	Restore HOMEBREW_LOG functionality	Max Howell

2012-09-25	Determine SUPERBIN correctly	Max Howell

2012-09-24	Abort if `xcrun -find foo` returns superbin/foo	Max Howell
	Fixes #14691. Rewrite in Ruby to facilitate checking PATHs properly.
2012-09-13	Make xcrun wrapper search /usr/bin too	Max Howell
	The usual xcrun would, and this wrapper exists to also work around broken xcode-select paths.
2012-09-01	Add mig tool to superenv	Max Howell
	Necessary because it otherwise calls actual cc after it does whatever it does. So we force it to call our cc.
2012-08-31	Refs #14558. Try to find tools when xcrun fails.	Max Howell

2012-08-29	superenv: build-environments that just work	Max Howell
	1. A minimal build environment, we don't set CFLAGS, CPPFLAGS, LDFLAGS, etc. the rationale being, the less that is set, the less variables we are introducing that can break builds. 2. A set of scripts that replace cc, ld, etc. and inject the -I, -L, etc. flags we need into the args passed to the build-tools. Because we now have complete control over compiler instantiations we do a variety of clean-up tasks, like removing bad flags, enforcing universal builds and ensuring makefiles don't try to change the order of library and include paths from ones that work to ones that don't. The previous ENV-system is still available when --env=std is specified. superenv applies to Xcode >= 4.3 only currently.