From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/5] gtest: Upgrade to GitHub HEAD
Date: Wed, 14 Oct 2015 23:55:22 +0200 [thread overview]
Message-ID: <20151014235522.774491e2@free-electrons.com> (raw)
In-Reply-To: <1444859483-2268-5-git-send-email-alan@softiron.co.uk>
Alan,
On Wed, 14 Oct 2015 17:51:22 -0400, Alan Ott wrote:
> +# The above revision must remain the same as the gmock package
> +GTEST_SITE = $(call github,google,googletest,$(GTEST_VERSION))
> GTEST_INSTALL_STAGING = YES
> GTEST_INSTALL_TARGET = NO
> GTEST_LICENSE = BSD-3c
> GTEST_LICENSE_FILES = LICENSE
> +GTEST_SUBDIR = googletest
So gtest and gmock are in fact now part of the same repository/upstream
project ? If that's the case, then I think we should simply get rid of
the gtest and gmock packages, and have a single package named
"googletest".
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-10-14 21:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 21:51 [Buildroot] [PATCH 0/5] Move download links away from Google Code Alan Ott
2015-10-14 21:51 ` [Buildroot] [PATCH 1/5] dsp-tools: Move download link " Alan Ott
2015-10-14 21:51 ` [Buildroot] [PATCH 2/5] gst-dsp: " Alan Ott
2015-10-14 21:51 ` [Buildroot] [PATCH 3/5] gst-omapfb: " Alan Ott
2015-10-14 21:51 ` [Buildroot] [PATCH 4/5] gtest: Upgrade to GitHub HEAD Alan Ott
2015-10-14 21:55 ` Thomas Petazzoni [this message]
2015-10-14 22:00 ` Alan Ott
2015-10-15 7:10 ` Thomas Petazzoni
2015-10-19 19:29 ` Carlos Santos
2016-02-17 18:17 ` Carlos Santos
2016-02-17 20:50 ` Thomas Petazzoni
2016-02-18 0:13 ` Alan Ott
2016-02-18 16:14 ` Carlos Santos
2016-02-18 16:18 ` Thomas Petazzoni
2016-02-18 19:26 ` Carlos Santos
2015-10-14 21:51 ` [Buildroot] [PATCH 5/5] gmock: " Alan Ott
2015-10-14 21:56 ` [Buildroot] [PATCH 0/5] Move download links away from Google Code Thomas Petazzoni
2015-10-14 22:02 ` Alan Ott
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=20151014235522.774491e2@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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.