From: Stephan Hoffmann <sho@relinux.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] New package: gtest
Date: Mon, 04 Mar 2013 11:28:49 +0100 [thread overview]
Message-ID: <51347761.2080700@relinux.de> (raw)
In-Reply-To: <1360088168-9012-1-git-send-email-sho@relinux.de>
Ping?
Am 05.02.2013 19:16, schrieb Stephan Hoffmann:
> Google's framework for writing C++ tests on a variety of platforms (Linux,
> Mac OS X, Windows, Cygwin, Windows CE, and Symbian). Based on the xUnit
> architecture. Supports automatic test discovery, a rich set of assertions,
> user-defined assertions, death tests, fatal and non-fatal failures, value-
> and type-parameterized tests, various options for running the tests, and XML
> test report generation.
>
> Gtest also allows to easily build testsuites for C programs.
>
> This package allows running testsuites on the target which might be
> advantgeous in certain cases.
>
> http://code.google.com/p/googletest/
>
> Signed-off-by: Stephan Hoffmann <sho@relinux.de>
> ---
> v2: Fixed whitespace errors
> v3: Renamed to gtest and fixed typos
>
> package/Config.in | 1 +
> package/gtest/Config.in | 20 ++++++++++++++++++++
> package/gtest/gtest.mk | 23 +++++++++++++++++++++++
> 3 files changed, 44 insertions(+), 0 deletions(-)
> create mode 100644 package/gtest/Config.in
> create mode 100644 package/gtest/gtest.mk
>
> diff --git a/package/Config.in b/package/Config.in
> index 2f219b6..845fe57 100644
> --- a/package/Config.in
> +++ b/package/Config.in
> @@ -541,6 +541,7 @@ source "package/fftw/Config.in"
> source "package/libargtable2/Config.in"
> source "package/argp-standalone/Config.in"
> source "package/boost/Config.in"
> +source "package/gtest/Config.in"
> source "package/libatomic_ops/Config.in"
> source "package/libcap/Config.in"
> source "package/libcap-ng/Config.in"
> diff --git a/package/gtest/Config.in b/package/gtest/Config.in
> new file mode 100644
> index 0000000..9064c6a
> --- /dev/null
> +++ b/package/gtest/Config.in
> @@ -0,0 +1,20 @@
> +config BR2_PACKAGE_GTEST
> + bool "gtest"
> + depends on BR2_USE_WCHAR && BR2_TOOLCHAIN_HAS_THREADS && BR2_INSTALL_LIBSTDCPP
> + help
> + Google's framework for writing C++ tests on a variety of platforms (Linux,
> + Mac OS X, Windows, Cygwin, Windows CE, and Symbian). Based on the xUnit
> + architecture. Supports automatic test discovery, a rich set of assertions,
> + user-defined assertions, death tests, fatal and non-fatal failures, value-
> + and type-parameterized tests, various options for running the tests, and XML
> + test report generation.
> +
> + Gtest also allows to easily build testsuites for C programs.
> +
> + This package allows running testsuites on the target which might be
> + advantageous in certain cases.
> +
> + http://code.google.com/p/googletest/
> +
> +comment "gtest requires a toolchain with c++, WCHAR and PTHREADS support"
> + depends on !BR2_USE_WCHAR || !BR2_TOOLCHAIN_HAS_THREADS || !BR2_INSTALL_LIBSTDCPP
> diff --git a/package/gtest/gtest.mk b/package/gtest/gtest.mk
> new file mode 100644
> index 0000000..4090c14
> --- /dev/null
> +++ b/package/gtest/gtest.mk
> @@ -0,0 +1,23 @@
> +#############################################################
> +#
> +# googletest
> +#
> +#############################################################
> +
> +GTEST_VERSION = 1.6.0
> +GTEST_SOURCE = gtest-1.6.0.zip
> +GTEST_SITE = http://googletest.googlecode.com/files/
> +GTEST_INSTALL_STAGING = YES
> +GTEST_INSTALL_TARGET = NO
> +
> +define GTEST_EXTRACT_CMDS
> + unzip $(DL_DIR)/$(GTEST_SOURCE) -d $(BUILD_DIR)
> +endef
> +
> +define GTEST_INSTALL_STAGING_CMDS
> + $(INSTALL) -D -m 0755 $(@D)/libgtest.a $(STAGING_DIR)/usr/lib/libgtest.a
> + $(INSTALL) -d -m 0755 $(STAGING_DIR)/usr/include/gtest/
> + cp -rp $(@D)/include/gtest/* $(STAGING_DIR)/usr/include/gtest/
> +endef
> +
> +$(eval $(cmake-package))
next prev parent reply other threads:[~2013-03-04 10:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 15:08 [Buildroot] [PATCH] New package: googletest Stephan Hoffmann
2013-02-05 15:18 ` [Buildroot] [PATCH v2] " Stephan Hoffmann
2013-02-05 15:47 ` Thomas Petazzoni
2013-02-05 16:27 ` Stephan Hoffmann
2013-02-05 16:57 ` Thomas Petazzoni
2013-02-05 17:01 ` Jeremy Rosen
2013-02-05 17:59 ` Stephan Hoffmann
2013-02-05 18:16 ` [Buildroot] [PATCH v3] New package: gtest Stephan Hoffmann
2013-03-04 10:28 ` Stephan Hoffmann [this message]
2013-03-17 22:22 ` Peter Korsgaard
2013-02-05 15:19 ` [Buildroot] [PATCH] New package: googletest Stephan Hoffmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51347761.2080700@relinux.de \
--to=sho@relinux.de \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.