From: Carlos Santos <casantos@datacom.ind.br>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] gtest: update recipe to use autotools
Date: Thu, 23 Apr 2015 08:23:47 -0300 (BRT) [thread overview]
Message-ID: <871078529.576418.1429788227635.JavaMail.zimbra@datacom.ind.br> (raw)
In-Reply-To: <20150422224620.7abefdb2@free-electrons.com>
> From: "Thomas Petazzoni" <thomas.petazzoni@free-electrons.com>
> To: "Carlos Santos" <casantos@datacom.ind.br>
> Cc: buildroot at buildroot.org
> Sent: Wednesday, April 22, 2015 5:46:20 PM
> Subject: Re: [Buildroot] [PATCH v2 1/1] gtest: update recipe to use autotools
> Dear Carlos Santos,
>
> On Wed, 22 Apr 2015 17:29:28 -0300, Carlos Santos wrote:
>
>> -$(eval $(cmake-package))
>> +$(eval $(autotools-package))
>
> I still don't understand. Fabio quoted the README of gtest, which says:
>
> """
> The Autotools build script (configure + make) is no longer officially
> supportted. You are encouraged to migrate to your own build system or
> use CMake.
> """
>
> So why moving from using the supported CMake to the no-longer supported
> autotools build system would be an improvement?
>
> This really needs more explanations.
I agree that using autotools is not the ideal approach but so I don't have a solution to generate the gtest-config script using CMake. I will spend some additional time on this today and submit and alternate patch if possible.
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com
Carlos Santos (Casantos)
DATACOM, P&D
next prev parent reply other threads:[~2015-04-23 11:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 12:52 [Buildroot] [PATCH 1/1] gtest: update recipe to use autotools Carlos Santos
2015-04-19 11:17 ` Fabio Porcedda
2015-04-22 20:20 ` Carlos Santos
2015-04-22 20:29 ` [Buildroot] [PATCH v2 " Carlos Santos
2015-04-22 20:46 ` Thomas Petazzoni
2015-04-23 11:23 ` Carlos Santos [this message]
2015-04-23 20:14 ` Arnout Vandecappelle
2015-04-25 9:25 ` 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=871078529.576418.1429788227635.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