From: Hongxu Jia <hongxu.jia@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 15/15] python-pycairo: fix buildpath QA issue
Date: Wed, 9 Mar 2016 09:05:52 +0800 [thread overview]
Message-ID: <56DF76F0.6020104@windriver.com> (raw)
In-Reply-To: <CAJTo0LbV7TfDKoZuT2OjV3PU7HaQ24DOpqZ2qGFOb0fhtXM9mA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1072 bytes --]
On 03/08/2016 11:26 PM, Burton, Ross wrote:
>
> On 26 February 2016 at 01:45, Hongxu Jia <hongxu.jia@windriver.com
> <mailto:hongxu.jia@windriver.com>> wrote:
>
> +do_unpack[postfuncs] += "unpack_waf"
> +do_unpack[vardeps] += "unpack_waf"
> +unpack_waf() {
> + # Just self extract tarball embedded in waf, do not care
> help message.
> + # Do not generate bytecode, becuase we need to patch
> python file later
> + PYTHONDONTWRITEBYTECODE=True ./waf --help >/dev/null
> +}
>
>
> Presumably this isn't pycairo-specific but impacts every recipe using waf?
>
> do_configure() {
> - BUILD_SYS=${BUILD_SYS} HOST_SYS=${HOST_SYS} ./waf
> configure --prefix=${D}${prefix} --libdir=${D}${libdir}
> + BUILD_SYS=${BUILD_SYS} HOST_SYS=${HOST_SYS} ./waf
> configure --prefix=${prefix} --libdir=${libdir}
> }
>
>
> Looks like this recipe needs to use the waf class for a start.
>
OK, I will try to merge these to waf.bbclass. V2 Incoming
//Hongxu
> Ross
[-- Attachment #2: Type: text/html, Size: 2903 bytes --]
next prev parent reply other threads:[~2016-03-09 1:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 1:44 [PATCH 00/15] fix python buildpaths QA issue Hongxu Jia
2016-02-26 1:44 ` [PATCH 07/15] insane:add buildpaths QA ignore pattern Hongxu Jia
2016-02-26 1:44 ` [PATCH 08/15] python2/3: fix buildpath QA issue Hongxu Jia
2016-02-26 1:44 ` [PATCH 09/15] bbclass distutils/distutils3: fix .pyc/.pyo buildpath Hongxu Jia
2016-02-26 1:44 ` [PATCH 10/15] python-setuptools/python3-setuptools: use old-style install Hongxu Jia
2016-02-26 1:44 ` [PATCH 11/15] python3-pip: " Hongxu Jia
2016-02-26 1:44 ` [PATCH 12/15] bbclass distutils/distutils3/setuptools/setuptools3: clean up DISTUTILS_INSTALL_ARGS Hongxu Jia
2016-02-26 1:45 ` [PATCH 13/15] python-pygobject: fix buildpath QA issue Hongxu Jia
2016-03-08 15:24 ` Burton, Ross
2016-03-08 15:27 ` Alexander Kanavin
2016-03-09 1:07 ` Hongxu Jia
2016-02-26 1:45 ` [PATCH 14/15] python-numpy: fix buildpaths " Hongxu Jia
2016-02-26 1:45 ` [PATCH 15/15] python-pycairo: fix buildpath " Hongxu Jia
2016-03-08 15:26 ` Burton, Ross
2016-03-09 1:05 ` Hongxu Jia [this message]
2016-03-09 1:11 ` [PATCH 00/15] fix python buildpaths " Hongxu Jia
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=56DF76F0.6020104@windriver.com \
--to=hongxu.jia@windriver.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 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.