| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2012-08-29 | Warn about removed warnings less shockingly | Max Howell | |
| The problem here now is though that the warnings only appear when compiling verbosely. But they should thus be visible if the build fails. Or if people are hunting for problems. | |||
| 2012-08-29 | Warn user if they set CFLAGS, etc. with superenv | Max Howell | |
| Since we remove some CFLAGS under their noses, this would otherwise be quite confusing. Notably, this will now trigger in numerous formula. Sucks. | |||
| 2012-08-29 | Superenv wrapper for sed | Max Howell | |
| Fixes Mountain Lion specific sed issue. Provided scripts don't use the full-path to see we are fine. They never do though, that would assume too much. | |||
| 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. | |||
