Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Hongxu Jia <hongxu.jia@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] qt4e.bbclass: export OE_QMAKE_QT_CONFIG
Date: Fri, 28 Jun 2013 20:49:20 +0800	[thread overview]
Message-ID: <51CD8650.7050806@windriver.com> (raw)
In-Reply-To: <20130628124534.GN3261@jama>

[-- Attachment #1: Type: text/plain, Size: 2330 bytes --]

On 06/28/2013 08:45 PM, Martin Jansa wrote:
> On Fri, Jun 28, 2013 at 01:40:26PM +0100, Paul Eggleton wrote:
>> On Friday 28 June 2013 14:28:56 Martin Jansa wrote:
>>> It's failing in my world builds too now, you can see log here:
>>> http://logs.nslu2-linux.org/buildlogs/oe/oe-shr-core-branches/log.world.2013
>>> 0627_214856.log/bitbake.log
>>>
>>> Cheers,
>>>
>>> On Fri, Jun 28, 2013 at 2:07 PM, Jonathan Liu <net147@gmail.com> wrote:
>>>> On 15/06/2013 10:06 AM, Jonathan Liu wrote:
>>>>> The class is inheriting qmake2.bbclass which exports OE_QMAKE_QT_CONFIG
>>>>> pointing to the qt4 qconfig.pri when it should be pointing to the
>>>>> qt4-embedded qconfig.pri.
>>>>>
>>>>> Signed-off-by: Jonathan Liu <net147@gmail.com>
>>>>> ---
>>>>>
>>>>>    meta/classes/qt4e.bbclass | 1 +
>>>>>    1 file changed, 1 insertion(+)
>>>>>
>>>>> diff --git a/meta/classes/qt4e.bbclass b/meta/classes/qt4e.bbclass
>>>>> index de2a68d..13b1050 100644
>>>>> --- a/meta/classes/qt4e.bbclass
>>>>> +++ b/meta/classes/qt4e.bbclass
>>>>> @@ -9,6 +9,7 @@ QT_LIBINFIX = "E"
>>>>>
>>>>>    # override variables set by qmake-base to compile Qt/Embedded apps
>>>>>    #
>>>>>    export QMAKESPEC = "${STAGING_DATADIR}/${QT_DIR_**
>>>>>
>>>>> NAME}/mkspecs/${TARGET_OS}-oe-**g++"
>>>>> +export OE_QMAKE_QT_CONFIG = "${STAGING_DATADIR}/${QT_DIR_**
>>>>> NAME}/mkspecs/qconfig.pri"
>>>>>
>>>>>    export OE_QMAKE_INCDIR_QT = "${STAGING_INCDIR}/${QT_DIR_**NAME}"
>>>>>    export OE_QMAKE_LIBDIR_QT = "${STAGING_LIBDIR}"
>>>>>    export OE_QMAKE_LIBS_QT = "qt"
>>>> Hi Saul,
>>>>
>>>> Do you have a log of the error you had building qt4-embedded with this
>>>> patch?
>> FWIW, I see the same error without this patch if I build qt4-embedded after
>> building qt4-x11, so I don't know if this patch is really related to the
>> problem or not.
> It was building fine in world builds until 1-2 weeks ago, but it's
> possible that I was just lucky to have it in right order.
>

Repoduce the bug by STEPS:

bitbake qt4-x11-free
bitbake qt4-embedded
and build qt4-embedded failed.

//Hongxu




>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core


[-- Attachment #2: Type: text/html, Size: 4681 bytes --]

  parent reply	other threads:[~2013-06-28 12:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-15  0:06 [PATCH] qt4e.bbclass: export OE_QMAKE_QT_CONFIG Jonathan Liu
2013-06-28 12:07 ` Jonathan Liu
2013-06-28 12:28   ` Martin Jansa
2013-06-28 12:40     ` Paul Eggleton
2013-06-28 12:45       ` Martin Jansa
2013-06-28 12:47         ` Paul Eggleton
2013-06-28 12:49         ` Hongxu Jia [this message]
2013-06-30 10:34           ` Martin Jansa
2013-06-30 11:44             ` Paul Eggleton

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=51CD8650.7050806@windriver.com \
    --to=hongxu.jia@windriver.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox