From: Carlos Santos <casantos@datacom.ind.br>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5] gtest/gmock: bump to version 1.8.0
Date: Sun, 12 Feb 2017 13:02:23 -0200 (BRST) [thread overview]
Message-ID: <116271.9983971.1486911743876.JavaMail.zimbra@datacom.ind.br> (raw)
In-Reply-To: <20170212153749.7f9aff72@free-electrons.com>
> From: "Thomas Petazzoni" <thomas.petazzoni@free-electrons.com>
> To: "Carlos Santos" <casantos@datacom.ind.br>
> Cc: buildroot at buildroot.org, "Fabrice Fontaine" <fabrice.fontaine@orange.com>, "romain naour" <romain.naour@gmail.com>,
> "yann morin 1998" <yann.morin.1998@free.fr>
> Sent: Sunday, February 12, 2017 12:37:49 PM
> Subject: Re: [Buildroot] [PATCH v5] gtest/gmock: bump to version 1.8.0
> Hello,
>
> On Sun, 12 Feb 2017 10:17:27 -0200, Carlos Santos wrote:
>
>> +define HOST_GTEST_INSTALL_CMDS
>> + $(INSTALL) -D -m 0755 $(@D)/googlemock/scripts/generator/gmock_gen.py \
>> + $(HOST_DIR)/usr/bin/gmock_gen.py
>> + ln -sf gmock_gen.py $(HOST_DIR)/usr/bin/gmock_gen
>
> Is there a good reason to not install directly gmock_gen.py as
> gmock_gen ?
IIRC some of out tests build calling gmock_gen.py and other calling gmock_gen
but I need to check that tomorrow, at office. Right now I'm at home, without
access to that code.
Carlos Santos (Casantos) - DATACOM, P&D
?Something must be done. This is something. Therefore we must do it.?
(from the BBC series ?Yes, Prime Minister?, ?Power to the people?)
next prev parent reply other threads:[~2017-02-12 15:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 14:39 [Buildroot] [PATCH 1/1] gtest: bump to version 1.8.0 Fabrice Fontaine
2016-09-07 15:19 ` Carlos Santos
2016-09-07 22:20 ` [Buildroot] [PATCH 1/1] gtest/gmock: " Carlos Santos
2016-09-07 23:16 ` [Buildroot] [PATCH v2] " Carlos Santos
2016-09-11 12:09 ` Arnout Vandecappelle
2017-02-06 15:43 ` Romain Naour
2017-02-06 16:46 ` Carlos Santos
2017-02-06 16:54 ` Romain Naour
2017-02-11 11:32 ` [Buildroot] [PATCH v3] " Carlos Santos
2017-02-11 13:50 ` Romain Naour
2017-02-11 18:08 ` Carlos Santos
2017-02-11 18:11 ` [Buildroot] [PATCH v4] " Carlos Santos
2017-02-12 12:17 ` [Buildroot] [PATCH v5] " Carlos Santos
2017-02-12 14:15 ` Romain Naour
2017-02-12 14:37 ` Thomas Petazzoni
2017-02-12 14:37 ` Thomas Petazzoni
2017-02-12 15:02 ` Carlos Santos [this message]
2017-02-12 17:28 ` Thomas Petazzoni
2017-02-14 11:05 ` [Buildroot] [PATCH v6] " Carlos Santos
2017-02-22 17:27 ` [Buildroot] [PATCH v7] " Carlos Santos
2017-02-26 14:05 ` Thomas Petazzoni
2017-02-27 12:31 ` Carlos Santos
2017-03-01 22:09 ` Thomas Petazzoni
2017-03-02 11:34 ` Carlos Santos
2017-03-05 21:17 ` [Buildroot] [PATCH v6] " Thomas Petazzoni
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=116271.9983971.1486911743876.JavaMail.zimbra@datacom.ind.br \
--to=casantos@datacom.ind.br \
--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