buildroot/package/gtest, branch 2016.02

gmock: new package

2015-10-03T15:11:01+00:00

Inspired by jMock, EasyMock, and Hamcrest, and designed with C++'s specifics in mind, Google C++ Mocking Framework (or Google Mock for short) is a library for writing and using C++ mock classes. Google Mock: * lets you create mock classes trivially using simple macros, * supports a rich set of matchers and actions, * handles unordered, partially ordered, or completely ordered expectations, * is extensible by users, and * works on Linux, Mac OS X, Windows, Windows Mobile, minGW, and Symbian. http://code.google.com/p/googlemock/ There are both host and target packages. The target one has include files required to compile the tests and the static libraries required to link/run them. The host package installs gmock_gen, a Python script used to generate code mocks. Notice that GMock 1.7.0 requires the Python 2 host package even if Python 3 is selected as a target package. Signed-off-by: Marcelo Barbosa Signed-off-by: Carlos Santos Reviewed-by: Romain Naour Signed-off-by: Peter Korsgaard

gtest: generate the gtest-config script

2015-04-25T09:22:42+00:00

gtest has moved from the autotools to CMake, but the CMake build system is currently not installing the gtest-config script. Work around that by installing it manually, after doing the necessary sed-ing from the gtest-config.in template. Reported-by: Carlos Santos Suggested-by: Arnout Vandecappelle Signed-off-by: Thomas Petazzoni

package/gtest: add hash

2015-04-19T21:10:27+00:00

Signed-off-by: Bernd Kuhls Signed-off-by: Thomas Petazzoni

gtest: install libgtest_main to staging

2015-01-25T17:45:20+00:00

gtest provides a separate libgtest_main library with a default main() implementation for tests with basic needs. This separate library isn't being installed by buildroot. This patch adds the installation of this library to staging during the install of gtest. Signed-off-by: Erico Nunes Signed-off-by: Thomas Petazzoni

unzip: Use the "-q" option to silence unzipping of source files

2014-11-02T21:48:50+00:00

Add and use the "UNZIP" variable instead of calling directly unzip because the variable contains the "-q" option to silence "unzip" so it doesn't show the list of files extracted just like when tar files are being unpacked. Signed-off-by: Fabio Porcedda Cc: Arnout Vandecappelle Signed-off-by: Peter Korsgaard

packages: rename FOO_CONF_OPT into FOO_CONF_OPTS

2014-10-04T16:54:16+00:00

To be consistent with the recent change of FOO_MAKE_OPT into FOO_MAKE_OPTS, make the same change for FOO_CONF_OPT. Sed command used: find * -type f | xargs sed -i 's#_CONF_OPT\>#&S#g' Signed-off-by: Thomas De Schampheleire Reviewed-by: "Yann E. MORIN" Signed-off-by: Thomas Petazzoni

package: remove the trailing slash sign from _SITE variable

2014-07-31T21:17:46+00:00

Since the trailing slash is stripped from $($(PKG)_SITE) by pkg-generic.mk: $(call DOWNLOAD,$($(PKG)_SITE:/=)/$($(PKG)_SOURCE)) so it is redundant. This patch removes it from $(PKG)_SITE variable for BR consistency. Signed-off-by: Jerzy Grzegorek Signed-off-by: Thomas Petazzoni

gtest: force static library build

2014-01-26T20:58:45+00:00

While it seems possible to build gtest as a shared library, using it in other projects requires to set some specific configuration flags in these projects for correctly linking against the shared version of the gtest library. So, to avoid bothering many projects and keep things as they were so far, we just force gtest to be built as a static library. Fixes: http://autobuild.buildroot.net/results/20cbf90749672607cb277c676a45d2c0c3965fa0/ http://autobuild.buildroot.net/results/5c6e58c51b2a14a7f23d296f771a76096b80362a/ http://autobuild.buildroot.net/results/bde777d343e9c4884272893d0da3b113dcc75e3a/ http://autobuild.buildroot.net/results/20cbf90749672607cb277c676a45d2c0c3965fa0/ http://autobuild.buildroot.net/results/89a29d1f597dbc12a6fc8eb079133a84952fc612/ Signed-off-by: Samuel Martin Signed-off-by: Peter Korsgaard

Config.in files: add missing dependencies to toolchain option comments

2013-11-10T22:59:57+00:00

When a package A depends on config option B and toolchain option C, then the comment that is given when C is not fulfilled should also depend on B. For example: config BR2_PACKAGE_A depends on BR2_B depends on BR2_LARGEFILE depends on BR2_WCHAR comment "A needs a toolchain w/ largefile, wchar" depends on !BR2_LARGEFILE || !BR2_WCHAR This comment should actually be: comment "A needs a toolchain w/ largefile, wchar" depends on BR2_B depends on !BR2_LARGEFILE || !BR2_WCHAR or if possible (typically when B is a package config option declared in that same Config.in file): if BR2_B comment "A needs a toolchain w/ largefile, wchar" depends on !BR2_LARGEFILE || !BR2_WCHAR [other config options depending on B] endif Otherwise, the comment would be visible even though the other dependencies are not met. This patch adds such missing dependencies, and changes existing such dependencies from depends on BR2_BASE_DEP && !BR2_TOOLCHAIN_USES_GLIBC to depends on BR2_BASE_DEP depends on !BR2_TOOLCHAIN_USES_GLIBC so that (positive) base dependencies are separate from the (negative) toolchain dependencies. This strategy makes it easier to write such comments (because one can simply copy the base dependency from the actual package config option), but also avoids complex and long boolean expressions. Signed-off-by: Thomas De Schampheleire Acked-by: Arnout Vandecappelle (Essensium/Mind) (untested) Signed-off-by: Peter Korsgaard

Config.in files: unify comments of toolchain option dependencies

2013-10-14T20:45:57+00:00

This patch lines up the comments in Config.in files that clarify which toolchain options the package depends on. Signed-off-by: Thomas De Schampheleire Signed-off-by: Peter Korsgaard