New package: googletest
PATCH 1/1 New package: googletest
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.
Googletest also allows to easily build testsuites for C programs.
This package allows running testsuites on the target which might be advanteous in certain cases.
http://code.google.com/p/googletest/
--- package/Config.in | 1 + package/gtest/Config.in | 22 ++++++++++++++++++++++ package/gtest/gtest.mk | 23 +++++++++++++++++++++++ 3 files changed, 46 insertions(+), 0 deletions(-) create mode 100644 package/gtest/Config.in create mode 100644 package/gtest/gtest.mk
package/Config.in +1 -0
@@ -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"
package/gtest/Config.in new file +22 -0
@@ -0,0 +1,22 @@ +config BR2_PACKAGE_GTEST + bool "googletest" + 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. + + Googletest also allows to easily build testsuites for C programs. + + This package allows running testsiuites on the target which might be + advanteous in certain cases. + + http://code.google.com/p/googletest/ + +comment "googletest requires a toolchain with c++, WCHAR and PTHREADS support" + depends on !BR2_USE_WCHAR || !BR2_TOOLCHAIN_HAS_THREADS || !BR2_INSTALL_LIBSTDCPP + +
package/gtest/gtest.mk new file +23 -0
@@ -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))
Signature · 1 line
1.7.0.4
PATCH v2 1/1 New package: googletest
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.
Googletest also allows to easily build testsuites for C programs.
This package allows running testsuites on the target which might be advanteous in certain cases.
http://code.google.com/p/googletest/
--- 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
package/Config.in +1 -0
@@ -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"
package/gtest/Config.in new file +20 -0
@@ -0,0 +1,20 @@ +config BR2_PACKAGE_GTEST + bool "googletest" + 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. + + Googletest also allows to easily build testsuites for C programs. + + This package allows running testsiuites on the target which might be + advanteous in certain cases. + + http://code.google.com/p/googletest/ + +comment "googletest requires a toolchain with c++, WCHAR and PTHREADS support" + depends on !BR2_USE_WCHAR || !BR2_TOOLCHAIN_HAS_THREADS || !BR2_INSTALL_LIBSTDCPP
package/gtest/gtest.mk new file +23 -0
@@ -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))
Signature · 1 line
1.7.0.4
PATCH v2 1/1 New package: googletest
Dear Stephan Hoffmann,
Quoted 11 lines · 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.
Googletest also allows to easily build testsuites for C programs.
This package allows running testsuites on the target which might be advanteous in certain cases.
Typo: advantageous.
package/gtest/Config.in line 1
Quoted 4 lines
package/gtest/Config.in new file +1
-0@@ -0,0 +1,20 @@ +config BR2_PACKAGE_GTEST
Maybe the package directory should be named "googletest" and the option BR2_PACKAGE_GOOGLETEST. But I'm not sure since the upstream tarball is just "gtest".
package/gtest/Config.in line 14
Quoted 13 lines
package/gtest/Config.in new file +13
-0+ bool "googletest" + 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. + + Googletest also allows to easily build testsuites for C programs. + + This package allows running testsiuites on the target which might be
testsuites
package/gtest/Config.in line 15
Quoted 1 line
package/gtest/Config.in new file +1
-0+ advanteous in certain cases.
advantageous
package/gtest/Config.in line 20
Quoted 5 lines
package/gtest/Config.in new file +5
-0+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
Even though I understand that it is composed only of a static library, I find this GTEST_INSTALL_TARGET = NO a bit strange. But well, ok.
package/gtest/Config.in
Quoted 4 lines
package/gtest/Config.in new file +4
-0+ +define GTEST_EXTRACT_CMDS + unzip $(DL_DIR)/$(GTEST_SOURCE) -d $(BUILD_DIR) +endef
Maybe some day we will want to have support in the package infrastructure to extract .zip files (we already have 3-4 packages that could benefit from this). But it can be done later.
package/gtest/Config.in
Quoted 5 lines
package/gtest/Config.in new file +5
-0+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
There's no "make install" or something like that?
Thanks,
Thomas
Signature · 4 lines
Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com
PATCH v2 1/1 New package: googletest
Am 05.02.2013 16:47, schrieb Thomas Petazzoni:
Quoted 16 lines
Dear Stephan Hoffmann,
Quoted 11 lines · 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.
Googletest also allows to easily build testsuites for C programs.
This package allows running testsuites on the target which might be advanteous in certain cases.
Typo: advantageous.
Quoted 7 lines
package/gtest/Config.in line 1
Quoted 4 lines
package/gtest/Config.in new file +1
-0@@ -0,0 +1,20 @@ +config BR2_PACKAGE_GTESTMaybe the package directory should be named "googletest" and the option
BR2_PACKAGE_GOOGLETEST. But I'm not sure since the upstream tarball is just "gtest".
Hello Thomas,
first I named it googletest, but since it is named gtest upstream and unzip produces a directory with this name I decided to changed it.
Quoted 19 lines
Quoted 4 lines
package/gtest/Config.in new file +3
-0+ bool "googletest" + depends on BR2_USE_WCHAR && BR2_TOOLCHAIN_HAS_THREADS && BR2_INSTALL_LIBSTDCPP + helppackage/gtest/Config.in line 14
Quoted 10 lines
package/gtest/Config.in new file +10
-0+ 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. + + Googletest also allows to easily build testsuites for C programs. + + This package allows running testsiuites on the target which might betestsuites
package/gtest/Config.in line 15
Quoted 1 line
package/gtest/Config.in new file +1
-0+ advanteous in certain cases.advantageous
Quoted 7 lines
package/gtest/Config.in line 20
Quoted 5 lines
package/gtest/Config.in new file +5
-0+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 = NOEven though I understand that it is composed only of a static library, I find this
GTEST_INSTALL_TARGET= NO a bit strange. But well, ok.
Yes, it is, but when there is nothing to install? Maybe it's also possible to compile it to a .so, but I am not sure if it's worth the effort. This way we can use googletest on the target and, when the testuites are not instaled, do not waste any space there.
BTW: Running googletest on the target out of eclipse works well.
Quoted 8 lines
package/gtest/Config.in
Quoted 5 lines
package/gtest/Config.in new file +4
-0+ +define GTEST_EXTRACT_CMDS + unzip $(DL_DIR)/$(GTEST_SOURCE) -d $(BUILD_DIR) +endefMaybe some day we will want to have support in the package infrastructure to extract .zip files (we already have 3-4 packages that could benefit from this). But it can be done later.
That would be nice.
Quoted 7 lines
package/gtest/Config.in
Quoted 6 lines
package/gtest/Config.in new file +5
-0+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/ +endefThere's no "make install" or something like that?
I didn't find any. Of course it would be nicer. As far as I understand the documentation one shall point the compiler and linker to the build directory.
Thanx for the review. I'll provide a fixed patch later.
Regards
Stephan
Quoted 4 lines
Thanks,
Thomas
Signature · 4 lines
reLinux - Stephan Hoffmann Am Schmidtgrund 124 50765 K?ln Tel. +49.221.95595-19 Fax: -64 www.reLinux.de sho at reLinux.de
PATCH v2 1/1 New package: googletest
Dear Stephan Hoffmann,
Quoted 11 lines · Stephan Hoffmann
Quoted 7 lines
package/gtest/Config.in line 1
Quoted 4 lines
package/gtest/Config.in new file +1
-0@@ -0,0 +1,20 @@ +config BR2_PACKAGE_GTESTMaybe the package directory should be named "googletest" and the option
BR2_PACKAGE_GOOGLETEST. But I'm not sure since the upstream tarball is just "gtest".Hello Thomas,
first I named it googletest, but since it is named gtest upstream and unzip produces a directory with this name I decided to changed it.
Ok. The fact that we don't control the unzip output directory is a bit annoying, but it's a separate matter.
In general we really try to keep a 1:1 mapping between:
* the option name
* the directory name
* the name of the label attached to the configuration option in the menuconfig
With the current proposal, people would see a "googletest" label in menuconfig, and might therefore look for package/googletest/... which won't exist.
Quoted 6 lines
Quoted 2 lines
Even though I understand that it is composed only of a static library, I find this
GTEST_INSTALL_TARGET= NO a bit strange. But well, ok.Yes, it is, but when there is nothing to install? Maybe it's also possible to compile it to a .so, but I am not sure if it's worth the effort. This way we can use googletest on the target and, when the testuites are not instaled, do not waste any space there.
Ok.
Quoted 1 line
BTW: Running googletest on the target out of eclipse works well.
Does it mean that you're using the Eclipse Buildroot plugin?
Quoted 3 lines
I didn't find any. Of course it would be nicer. As far as I understand the documentation one shall point the compiler and linker to the build directory.
Ok.
Thomas
Signature · 4 lines
Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com
PATCH v2 1/1 New package: googletest
on a slightly related note, the gperftools were previously known as googleperftools
so I think settling for gtest rather than googletest would make sense since its the direction google seems to be generally moving
Cordialement
J?r?my Rosen
fight key loggers : write some perl using vim
----- Mail original -----
Quoted 68 lines
Dear Stephan Hoffmann,
Quoted 9 lines · Stephan Hoffmann
Quoted 9 lines
package/gtest/Config.in line 1
Quoted 4 lines
package/gtest/Config.in new file +1
-0@@ -0,0 +1,20 @@ +config BR2_PACKAGE_GTESTMaybe the package directory should be named "googletest" and the option
BR2_PACKAGE_GOOGLETEST. But I'm not sure since the upstream tarball is
just "gtest".Quoted 5 lines
Hello Thomas,
first I named it googletest, but since it is named gtest upstream and
unzip produces a directory with this name I decided to changed it.Ok. The fact that we don't control the unzip output directory is a bit
annoying, but it's a separate matter.In general we really try to keep a 1:1 mapping between:
* the option name
* the directory name
* the name of the label attached to the configuration option in the menuconfigWith the current proposal, people would see a "googletest" label in menuconfig, and might therefore look for package/googletest/... which won't exist.
Quoted 9 lines
Quoted 4 lines
Even though I understand that it is composed only of a static library,
I find thisGTEST_INSTALL_TARGET= NO a bit strange. But well, ok.Yes, it is, but when there is nothing to install? Maybe it's also possible to compile it to a .so, but I am not sure if it's worth the
effort. This way we can use googletest on the target and, when the testuites are not instaled, do not waste any space there.Ok.
Quoted 1 line
BTW: Running googletest on the target out of eclipse works well.
Does it mean that you're using the Eclipse Buildroot plugin?
Quoted 5 lines
I didn't find any. Of course it would be nicer. As far as I understand
the documentation one shall point the compiler and linker to the build
directory.Ok.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
PATCH v2 1/1 New package: googletest
In reply to Thomas PetazzoniAm 05.02.2013 17:57, schrieb Thomas Petazzoni:
Quoted 24 lines
Dear Stephan Hoffmann,
Quoted 11 lines · Stephan Hoffmann
Quoted 7 lines
package/gtest/Config.in line 1
Quoted 4 lines
package/gtest/Config.in new file +1
-0@@ -0,0 +1,20 @@ +config BR2_PACKAGE_GTESTMaybe the package directory should be named "googletest" and the option
BR2_PACKAGE_GOOGLETEST. But I'm not sure since the upstream tarball is just "gtest".Hello Thomas,
first I named it googletest, but since it is named gtest upstream and unzip produces a directory with this name I decided to changed it.
Ok. The fact that we don't control the unzip output directory is a bit annoying, but it's a separate matter.
In general we really try to keep a 1:1 mapping between:
* the option name
* the directory name
* the name of the label attached to the configuration option in the menuconfig
Quoted 3 lines
With the current proposal, people would see a "googletest" label in menuconfig, and might therefore look for package/googletest/... which won't exist.
That's right, I think I'll name it gtest everywhere, as also Jeremy Rosen proposes.
Quoted 11 lines
Quoted 7 lines
Quoted 3 lines
Even though I understand that it is composed only of a static library, I find this
GTEST_INSTALL_TARGET= NO a bit strange. But well, ok.Yes, it is, but when there is nothing to install? Maybe it's also possible to compile it to a .so, but I am not sure if it's worth the effort. This way we can use googletest on the target and, when the testuites are not instaled, do not waste any space there.
Ok.
Quoted 1 line
BTW: Running googletest on the target out of eclipse works well.
Does it mean that you're using the Eclipse Buildroot plugin?
Yes, I played around with it a little and I like it. It gives a real jumpstart into cross development for buildroot targets.
Quoted 6 lines
Quoted 3 lines
I didn't find any. Of course it would be nicer. As far as I understand the documentation one shall point the compiler and linker to the build directory.
Ok.
Thomas
Signature · 4 lines
reLinux - Stephan Hoffmann Am Schmidtgrund 124 50765 K?ln Tel. +49.221.95595-19 Fax: -64 www.reLinux.de sho at reLinux.de
PATCH v3 1/1 New package: gtest
In reply to Stephan HoffmannGoogle'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/
---
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
package/Config.in +1 -0
@@ -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"
package/gtest/Config.in new file +20 -0
@@ -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
package/gtest/gtest.mk new file +23 -0
@@ -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))
Signature · 1 line
1.7.0.4
PATCH v3 1/1 New package: gtest
Ping?
Am 05.02.2013 19:16, schrieb Stephan Hoffmann:
Quoted 93 lines
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 <[email protected]>---
v2: Fixed whitespace errors
v3: Renamed to gtest and fixed typospackage/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.mkpackage/Config.in +1
-0@@ -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"package/gtest/Config.in new file +20
-0@@ -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_LIBSTDCPPpackage/gtest/gtest.mk new file +23
-0@@ -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))
PATCH v3 1/1 New package: gtest
In reply to Stephan HoffmannQuoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Stephan" == Stephan Hoffmann <[email protected]> writes:
Stephan> Google's framework for writing C++ tests on a variety of Stephan> platforms (Linux, Mac OS X, Windows, Cygwin, Windows CE, and Stephan> Symbian). Based on the xUnit architecture. Supports automatic Stephan> test discovery, a rich set of assertions, user-defined Stephan> assertions, death tests, fatal and non-fatal failures, value- Stephan> and type-parameterized tests, various options for running the Stephan> tests, and XML test report generation.
Stephan> Gtest also allows to easily build testsuites for C programs.
Stephan> This package allows running testsuites on the target which might be Stephan> advantgeous in certain cases.
Stephan> http://code.google.com/p/googletest/
Stephan> Signed-off-by: Stephan Hoffmann <[email protected]> Stephan> ---
Stephan> v2: Fixed whitespace errors
Stephan> v3: Renamed to gtest and fixed typos
Stephan> package/Config.in | 1 + Stephan> package/gtest/Config.in | 20 ++++++++++++++++++++ Stephan> package/gtest/gtest.mk | 23 +++++++++++++++++++++++ Stephan> 3 files changed, 44 insertions(+), 0 deletions(-) Stephan> create mode 100644 package/gtest/Config.in Stephan> create mode 100644 package/gtest/gtest.mk
Stephan> diff --git a/package/Config.in b/package/Config.in Stephan> index 2f219b6..845fe57 100644
Stephan> --- a/package/Config.in
Stephan> +++ b/package/Config.in
Stephan> @@ -541,6 +541,7 @@ source "package/fftw/Config.in"
Stephan> source "package/libargtable2/Config.in" Stephan> source "package/argp-standalone/Config.in" Stephan> source "package/boost/Config.in" Stephan> +source "package/gtest/Config.in" Stephan> source "package/libatomic_ops/Config.in" Stephan> source "package/libcap/Config.in" Stephan> source "package/libcap-ng/Config.in"
Stephan> diff --git a/package/gtest/Config.in b/package/gtest/Config.in Stephan> new file mode 100644
Stephan> index 0000000..9064c6a
Stephan> --- /dev/null
Stephan> +++ b/package/gtest/Config.in
Stephan> @@ -0,0 +1,20 @@
Stephan> +config BR2_PACKAGE_GTEST
Stephan> + bool "gtest"
Stephan> + depends on BR2_USE_WCHAR && BR2_TOOLCHAIN_HAS_THREADS && BR2_INSTALL_LIBSTDCPP
We normally have seperate 'depends on' for each individual dependency.
Stephan> + help
Stephan> + Google's framework for writing C++ tests on a variety of platforms (Linux, Stephan> + Mac OS X, Windows, Cygwin, Windows CE, and Symbian). Based on the xUnit Stephan> + architecture. Supports automatic test discovery, a rich set of assertions, Stephan> + user-defined assertions, death tests, fatal and non-fatal failures, value- Stephan> + and type-parameterized tests, various options for running the tests, and XML Stephan> + test report generation.
I've word wrapped this to fit inside ~70 chars.
Stephan> +comment "gtest requires a toolchain with c++, WCHAR and PTHREADS support"
Stephan> + depends on !BR2_USE_WCHAR || !BR2_TOOLCHAIN_HAS_THREADS || !BR2_INSTALL_LIBSTDCPP
We normally just talk about threads support, as it can come from pthreads or nptl.
Stephan> diff --git a/package/gtest/gtest.mk b/package/gtest/gtest.mk Stephan> new file mode 100644
Stephan> index 0000000..4090c14
Stephan> --- /dev/null
Stephan> +++ b/package/gtest/gtest.mk
Stephan> @@ -0,0 +1,23 @@
Stephan> +############################################################# Stephan> +#
Stephan> +# googletest
Stephan> +#
Stephan> +############################################################# Stephan> +
Stephan> +GTEST_VERSION = 1.6.0
Stephan> +GTEST_SOURCE = gtest-1.6.0.zip
This should be GTEST_SOURCE = gtest-$(GTEST_SOURCE).zip
Stephan> +GTEST_SITE = http://googletest.googlecode.com/files/
Stephan> +GTEST_INSTALL_STAGING = YES
Stephan> +GTEST_INSTALL_TARGET = NO
Stephan> +
Stephan> +define GTEST_EXTRACT_CMDS
Stephan> + unzip $(DL_DIR)/$(GTEST_SOURCE) -d $(BUILD_DIR)
Stephan> +endef
Double space after unzip.
Committed with these fixes, thanks.
Signature · 1 line
Bye, Peter Korsgaard
PATCH 1/1 New package: googletest
In reply to Stephan HoffmannThere are whitespace errors within, please discard. v2 is on the way.
Am 05.02.2013 16:08, schrieb Stephan Hoffmann:
Quoted 92 lines
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.
Googletest also allows to easily build testsuites for C programs.
This package allows running testsuites on the target which might be advanteous in certain cases.
http://code.google.com/p/googletest/
Signed-off-by Stephan Hoffmann <[email protected]>--- package/Config.in | 1 + package/gtest/Config.in | 22 ++++++++++++++++++++++ package/gtest/gtest.mk | 23 +++++++++++++++++++++++ 3 files changed, 46 insertions(+), 0 deletions(-) create mode 100644 package/gtest/Config.in create mode 100644 package/gtest/gtest.mkpackage/Config.in +1
-0@@ -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"package/gtest/Config.in new file +22
-0@@ -0,0 +1,22 @@ +config BR2_PACKAGE_GTEST + bool "googletest" + 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. + + Googletest also allows to easily build testsuites for C programs. + + This package allows running testsiuites on the target which might be + advanteous in certain cases. + + http://code.google.com/p/googletest/ + +comment "googletest requires a toolchain with c++, WCHAR and PTHREADS support" + depends on !BR2_USE_WCHAR || !BR2_TOOLCHAIN_HAS_THREADS || !BR2_INSTALL_LIBSTDCPP + +package/gtest/gtest.mk new file +23
-0@@ -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))
Signature · 4 lines
reLinux - Stephan Hoffmann Am Schmidtgrund 124 50765 K?ln Tel. +49.221.95595-19 Fax: -64 www.reLinux.de sho at reLinux.de