homebrew-core/Formula/unittest.rb

require 'formula'

class Unittest <Formula
  @url='http://unittest.red-bean.com/tar/unittest-0.50-62.tar.gz'
  @homepage='http://unittest.red-bean.com/'
  @md5='6eaa2823620c2e21fc745bd8da6a26b2'

  def install
    fails_with_llvm
    system "./configure", "--prefix=#{prefix}", "--disable-debug", "--disable-dependency-tracking"
    system "make install"
  end
end
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 08:07:12 +00:00			`require 'formula'`
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-08 08:38:38 +00:00
			`class Unittest <Formula`
			`@url='http://unittest.red-bean.com/tar/unittest-0.50-62.tar.gz'`
			`@homepage='http://unittest.red-bean.com/'`
			`@md5='6eaa2823620c2e21fc745bd8da6a26b2'`

			`def install`
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 18:50:36 +00:00			`fails_with_llvm`
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-08 08:38:38 +00:00			`system "./configure", "--prefix=#{prefix}", "--disable-debug", "--disable-dependency-tracking"`
			`system "make install"`
			`end`
			`end`