From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/5] gtest: Upgrade to GitHub HEAD
Date: Thu, 15 Oct 2015 09:10:30 +0200 [thread overview]
Message-ID: <20151015091030.2f7272ec@free-electrons.com> (raw)
In-Reply-To: <561ED08C.5010301@softiron.co.uk>
Dear Alan Ott,
On Wed, 14 Oct 2015 18:00:44 -0400, Alan Ott wrote:
> > 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".
>
> Yes, that would probably be better. gmock depends on gtest, and gtest
> can be standalone. Maybe we have one package with a submenu option to
> build each target (and a dependency so gmock selects gtest).
>
> Is that ok by you?
Yes, that's OK.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-10-15 7:10 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
2015-10-14 22:00 ` Alan Ott
2015-10-15 7:10 ` Thomas Petazzoni [this message]
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=20151015091030.2f7272ec@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox