Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/4] xcb-proto: create .pyc files for python2
Date: Thu, 13 Oct 2016 11:19:35 +0800	[thread overview]
Message-ID: <ff63db29-b4fd-332a-889c-68dacddb6dcc@windriver.com> (raw)
In-Reply-To: <CAJTo0LYA0ZPi23Avt1=tyMq4_bDSZui-gdQwWcq1gbJN3B2U4Q@mail.gmail.com>



On 10/12/2016 07:36 PM, Burton, Ross wrote:
>
> On 12 October 2016 at 07:31, Robert Yang <liezhi.yang@windriver.com
> <mailto:liezhi.yang@windriver.com>> wrote:
>
>     +    cd  ${D}${libdir}/xcb-proto/xcbgen
>     +    python -m py_compile *.py
>
>
> The cd is redundant as you can pass absolute paths to py_compile.

Thanks, updated in the repo:

   git://git.openembedded.org/openembedded-core-contrib rbt/4fixes
   http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=rbt/4fixes

Robert Yang (4):
   xcb-proto: create .pyc files for python2
   xcb-proto: fix for python3
   libxcb: use python3 to build it
   source-highlight: use with-boost-libdir

// Robert

>
> Ross


  reply	other threads:[~2016-10-13  3:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-12  6:31 [PATCH 0/4] fix xcb-proto libxcb and source-highlight Robert Yang
2016-10-12  6:31 ` [PATCH 1/4] xcb-proto: create .pyc files for python2 Robert Yang
2016-10-12  8:00   ` Jussi Kukkonen
2016-10-12  8:20     ` Robert Yang
2016-10-12 11:36   ` Burton, Ross
2016-10-13  3:19     ` Robert Yang [this message]
2016-10-12  6:31 ` [PATCH 2/4] xcb-proto: fix for python3 Robert Yang
2016-10-12  6:31 ` [PATCH 3/4] libxcb: use python3 to build it Robert Yang
2016-10-12  6:31 ` [PATCH 4/4] source-highlight: use with-boost-libdir 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=ff63db29-b4fd-332a-889c-68dacddb6dcc@windriver.com \
    --to=liezhi.yang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox