From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Parse errors introduce by qt4 python->shell style functions
Date: Sun, 17 Jun 2012 10:23:28 +0100 [thread overview]
Message-ID: <1339925008.8481.3.camel@ted> (raw)
In-Reply-To: <20120617090351.GA21623@ad.chargestorm.se>
On Sun, 2012-06-17 at 11:03 +0200, Anders Darander wrote:
> Hi,
>
> I recently started to look at updating our internal repos using the
> latest denzil updates.
>
> However, this introduced parse errors for us. We got a bbappend for
> qt4-embedded, which includes a number of lines like:
>
> QT_CONFIG_FLAGS := "${@oe_filter_out('-plugin-gfx-transformed',
> '${QT_CONFIG_FLAGS}', d)}"
>
> (this is to remove lots of features, both size-wise and to reduce build
> time).
>
> This work fine up to the original denzil release. Now I've run a bisect,
> and found that our problems was introduced by "qt4: move functions from
> python to shell style", commit id:
> 98cb2efe4e9f3092d531c9fc809406c3ef559725.
>
> After this commit, we get errors like:
> $ bitbake core-image-sato -eLoading cache: 100%
> |###################################################| ETA: 00:00:00
> Loaded 1109 entries from dependency cache.
> ERROR: Failure expanding variable QT_CONFIG_FLAGS[:=], expression was
> ${@oe_filter_out('-plugin-gfx-transformed', ' -embedded ${QT_ARCH}
Where is QT_ARCH coming from?
Looking at the way the code now works, I have a suspicion that we should
change that to $QT_ARCH and that might fix your problem. I'm just
guessing though.
Cheers,
Richard
next prev parent reply other threads:[~2012-06-17 9:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-17 9:03 Parse errors introduce by qt4 python->shell style functions Anders Darander
2012-06-17 9:23 ` Richard Purdie [this message]
2012-06-17 11:19 ` Anders Darander
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=1339925008.8481.3.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
/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.