From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gmock: download from github and convert to a cmake-package
Date: Thu, 8 Sep 2016 21:20:33 +0200 [thread overview]
Message-ID: <20160908212033.1d1c6947@free-electrons.com> (raw)
In-Reply-To: <1473353883-10762-1-git-send-email-casantos@datacom.ind.br>
Hello,
On Thu, 8 Sep 2016 13:58:03 -0300, Carlos Santos wrote:
> +--- ./CMakeLists.txt.orig 2013-09-18 21:32:04.000000000 -0300
> ++++ ./CMakeLists.txt 2016-09-08 11:10:51.519780433 -0300
> +@@ -15,7 +15,7 @@
> + if (EXISTS "${CMAKE_CURRENT_SOURCE_DIR}/gtest/CMakeLists.txt")
> + set(gtest_dir gtest)
> + else()
> +- set(gtest_dir ../gtest)
> ++ set(gtest_dir ../gtest-${GTEST_VERSION})
So you make the assumption that you have the following code
organization:
output/build/gmock-1.7.0
output/build/gtest-1.7.0
i.e, during its build process, gmock needs to access the gtest source
code?
Why is it the case? As far as I'm aware, it's not currently the case
with the existing packaging.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-09-08 19:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 16:24 [Buildroot] [PATCH 6/6] gtest: retrieve package from github Fabrice Fontaine
2016-09-06 13:58 ` Carlos Santos
2016-09-06 20:40 ` Arnout Vandecappelle
[not found] ` <29481_1473259225_57D026D9_29481_7433_1_EEB3FED4859B6C488DDDEC4B2D3DE92B0FCC280F@OPEXCLILM23.corporate.adroot.infra.ftgroup>
2016-09-07 23:03 ` Carlos Santos
2016-09-07 23:22 ` Carlos Santos
2016-09-08 16:58 ` [Buildroot] [PATCH] gmock: download from github and convert to a cmake-package Carlos Santos
2016-09-08 19:20 ` Thomas Petazzoni [this message]
2016-09-08 20:11 ` Carlos Santos
2016-09-08 20:14 ` Thomas Petazzoni
2016-09-08 20:34 ` Carlos Santos
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=20160908212033.1d1c6947@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.