Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>,
	Christopher Larson <clarson@kergoth.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 7/8] autotools.bbclass: use relative path to run configure script
Date: Fri, 9 Oct 2015 09:28:40 +0800	[thread overview]
Message-ID: <56171848.4010805@windriver.com> (raw)
In-Reply-To: <CAJTo0Lbe64X4-vG4uBfypz9zDREU6vYiU0LWNk1aFe+CHYzZYg@mail.gmail.com>


Hi Chris and Ross,

On 10/09/2015 05:06 AM, Burton, Ross wrote:
>
> On 8 October 2015 at 22:00, Christopher Larson <clarson@kergoth.com
> <mailto:clarson@kergoth.com>> wrote:
>
>             +       # Use relative path for S to avoid buildpaths in files
>             +       relative_s=`python -c "import os; print
>             os.path.relpath('${S}', '.')"`
>             +       cfgscript="$relative_s/configure"
>
>
>         Why not just use inline python here, rather than calling out to an
>         external python process at task execution time?
>
>
>     Oh, nevermind, of course oe_runconf can be run from any number of paths :)

Yes, "inline python" is executed at parsing time, but we need it be
a building time path.

>
>
> Why not use realpath?
>
> ross@flashheart ~/Yocto/poky/meta/recipes-devtools/qemu (mut)
> $ realpath --relative-to=. ~/Yocto/poky/meta/recipes-support/mpfr/
> ../../recipes-support/mpfr

I'm afraid that realpath is not generally existed on the build host ?

// Robert

>
> Ross


  reply	other threads:[~2015-10-09  1:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-08 13:16 [YOCTO 2.1] [PATCH 0/8] fixes for package_qa_walk() and buildpaths Robert Yang
2015-10-08 13:16 ` [PATCH 1/8] insane.bbclass: do_package_qa depends on WARN_QA and ERROR_QA Robert Yang
2015-10-08 13:16 ` [PATCH 2/8] insane.bbclass: make package_qa_walk() can print all the messages Robert Yang
2015-10-08 13:16 ` [PATCH 3/8] insane.bbclass: buildpaths: ignore .pyc files Robert Yang
2015-10-08 13:16 ` [PATCH 4/8] insane.bbclass: skip buildpath qa check when set INHIBIT_PACKAGE_STRIP Robert Yang
2015-10-08 13:16 ` [PATCH 5/8] insane.bbclass: fix for ignoring debug files Robert Yang
2015-10-08 13:16 ` [PATCH 6/8] package.bbclass: strip archive files Robert Yang
2015-10-08 13:16 ` [PATCH 7/8] autotools.bbclass: use relative path to run configure script Robert Yang
2015-10-08 21:00   ` Christopher Larson
2015-10-08 21:00     ` Christopher Larson
2015-10-08 21:06       ` Burton, Ross
2015-10-09  1:28         ` Robert Yang [this message]
2015-10-09 10:51           ` Burton, Ross
2015-10-09 11:30             ` Robert Yang
2015-10-13  7:08               ` Paul Eggleton
2015-10-13  7:17                 ` Robert Yang
2015-10-13  7:30                   ` Paul Eggleton
2015-10-08 13:16 ` [PATCH 8/8] glibc-initial.inc: use relative path to run configure Robert Yang

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=56171848.4010805@windriver.com \
    --to=liezhi.yang@windriver.com \
    --cc=clarson@kergoth.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