Commit graph

9 commits

Author SHA1 Message Date
Jack Nagel
89b2018d80 Update bare fails_with_llvm calls
These formulae all compile and run with LLVM build >= 2335.

Signed-off-by: Jack Nagel <jacknagel@gmail.com>
2011-10-28 15:52:44 -05:00
Adam Vandenberg
99b61b9a23 Update fails_with_llvm in formulae 2011-03-25 23:31:30 -07:00
Adam Vandenberg
4147b05c57 Use ruby style for inheritance. 2011-03-12 11:55:09 -08:00
George Kulakowski
db9bd5a7b1 Fix unittest md5
Signed-off-by: Adam Vandenberg <flangy@gmail.com>
2011-02-22 14:10:12 -08:00
Adam Vandenberg
7bd947eb0b Update formulae for version 0.7
* Use new "url" features
* Use keg_only DSL
* Use "skip_clean :all" DSL
* Whitespace and style cleanups
* Make bash invocations less silly
* Use new man2-man8 helpers
* Remove "FileUtils." since it is included in Formula
* Use real names for deps instead of aliases
* ENV.x11 now updates path, so remove that from individual brews
2010-08-07 18:08:53 -07:00
Adam Vandenberg
e1bb919734 Add "fails_with_llvm" to formula to document LLVM build breaks.
Replaced ENV.gcc_4_2 + comments with calls to "fails_with_llvm",
to specifically message to the user when a formula is known or suspected
to not build with LLVM. If the user specifies "--use-llvm", the message
will be displayed, but compilation will be tried anyway.

Since using LLVM is now an advanced/hidden feature instead of the
default on 10.6, we'll let the user try anyway (and submit patches
if things are now working.)
2010-06-16 11:50:36 -07:00
Adam Vandenberg
4cce89ebe2 Use gcc for unittest, so its own tests pass. 2010-02-16 22:15:24 -08:00
Max Howell
61b2307139 s/require 'brewkit'/require 'formula'/g
brewkit.rb changes ENV destructively, so lets not do that everytime a formula
is required. Now it's possible for other tools to require a formula
description without worrying about side-effects.
2009-10-15 16:48:03 +01:00
Dane Jensen
abb5511357 Unittest formula
This is the web page for a C++ unit test framework. Its design goals are to be
simple, to be idiomatic C++, and to follow the basic xUnit style to the extent
that doing so is compatible with the earlier goals. Its main differences from
other xUnit frameworks are that it uses constructors and destructors for
setup/teardown and that it requires you to represent tests as classes, instead
of methods.
2009-09-16 14:49:06 +01:00