From: "Miroslav Keš" <miroslav.kes@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: cmake: respect ${S} and ${B} patch problem
Date: Fri, 13 Jun 2014 18:51:51 +0200 [thread overview]
Message-ID: <539B2C27.4070803@gmail.com> (raw)
In-Reply-To: <CAJTo0Lauenh9=Mep+4ZUVPnjf0yJDdaCxbrNcB5vXEmtjn5-iA@mail.gmail.com>
On 06/13/14 18:38, Burton, Ross wrote:
> On 13 June 2014 17:33, Miroslav Keš <miroslav.kes@gmail.com> wrote:
>> + if [ -z "${OECMAKE_SOURCEPATH}" ]; then
>> + OECMAKE_SOURCEPATH="${S}"
>> fi
>>
>> if [ "${S}" != "${B}" ]; then
>> @@ -84,7 +88,7 @@ cmake_do_configure() {
>>
>> cmake \
>> ${OECMAKE_SITEFILE} \
>> - ${S} \
>> + ${OECMAKE_SOURCEPATH} \
> A better idiom that's more self-documenting would be to set
> OECMAKE_SOURCEPATH ?= "${S}" at the top-level.
You are right.
> Would it be sensible to give that variable a different name as it
> refers specifically to the location of the cmake file, and not the
> rest of the source?
I was thinking about a better name too.
The reason why I stayed with the OECMAKE_SOURCEPATH is that the cmake
man page says:
USAGE
cmake [options] <path-to-source>
And that's the directory that I want to set. So I thought that it would
be understandable for people familiar with cmake.
Mira
> Ross
next prev parent reply other threads:[~2014-06-13 16:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 16:33 cmake: respect ${S} and ${B} patch problem Miroslav Keš
2014-06-13 16:38 ` Burton, Ross
2014-06-13 16:51 ` Miroslav Keš [this message]
2014-06-17 20:20 ` Miroslav Keš
2014-06-17 20:36 ` Saul Wold
2014-06-19 19:39 ` [PATCH v2] " Miroslav Keš
2014-06-24 20:23 ` Burton, Ross
2014-06-17 21:21 ` Burton, Ross
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=539B2C27.4070803@gmail.com \
--to=miroslav.kes@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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