All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Busch <morphis@gravedo.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: qt-x11-free_7.7.2 fail configure missing qmake
Date: Sun, 15 May 2011 14:15:00 +0200	[thread overview]
Message-ID: <4DCFC3C4.506@gravedo.de> (raw)
In-Reply-To: <4DCFC1B6.6090808@gravedo.de>

On 15.05.2011 14:06, Simon Busch wrote:
> On 13.05.2011 21:35, Eric Bénard wrote:
>> Hi,
>>
>>> On 13/05/2011 16:28, Eivind Kvedalen wrote:
>>>> I get the same problem here when trying to compile
>>>> qt4-embedded_4.7.2.bb.
>>>>
>>>> Build Configuration:
>>>> BB_VERSION = "1.10.2"
>>>> METADATA_BRANCH = "master"
>>>> METADATA_REVISION = "54ab33e"
>>>> TARGET_ARCH = "arm"
>>>> TARGET_OS = "linux-gnueabi"
>>>> MACHINE = "beagleboard"
>>>> DISTRO = "angstrom"
>>>> DISTRO_VERSION = "v2011.05"
>>>> TARGET_FPU = "hard"
>>>>
>> problem reproduced with a clean tmp.
>> this patch restore a part that 5a6efd58cdc85d08ab9e106c84bbac5110b5aecd
>> removed in do_install which seems to be the root of the problem.
> 
> I tested this with
> 
> # bitbake qt4-native && bitbake qt4-x11-free
> 
> and both builds succceeded. Only the qt4-x11-free build prints some
> WARNINGS I didn't discoverd before:
> 
> 
> WARNING: the following files were installed but not shipped in any package:
> WARNING:   /usr/imports/Qt/labs/particles/libqmlparticlesplugin.so
> WARNING:   /usr/imports/Qt/labs/particles/qmldir
> WARNING:   /usr/imports/Qt/labs/particles/.debug/libqmlparticlesplugin.so
> WARNING:
> /usr/imports/Qt/labs/folderlistmodel/libqmlfolderlistmodelplugin.so
> WARNING:   /usr/imports/Qt/labs/folderlistmodel/qmldir
> WARNING:
> /usr/imports/Qt/labs/folderlistmodel/.debug/libqmlfolderlistmodelplugin.so
> WARNING:   /usr/imports/Qt/labs/gestures/libqmlgesturesplugin.so
> WARNING:   /usr/imports/Qt/labs/gestures/qmldir
> WARNING:   /usr/imports/Qt/labs/gestures/.debug/libqmlgesturesplugin.so
> WARNING:   /usr/imports/QtWebKit/libqmlwebkitplugin.so
> WARNING:   /usr/imports/QtWebKit/qmldir
> WARNING:   /usr/imports/QtWebKit/.debug/libqmlwebkitplugin.so
> WARNING:   /usr/lib/fonts/fontdir
> WARNING:   /usr/lib/qt4/plugins/qmltooling/libtcpserver.so
> WARNING:   /usr/lib/qt4/plugins/qmltooling/.debug/libtcpserver.so
> 
> As this are some quite relevant components (like the QML webkit plugin)
> they should really get packaged by our qt4-x11-free recipe. Will see if
> I have the time to provide a patch for this too.
> 
> Will send a patch with my changes to the qt4-native.inc file (which are
> mostly the same as Eric did) after this mail.

Hm, ok someone was fast than me and already commited the patch without
mention it here. Thanks Eric!

regards,
Simon



      parent reply	other threads:[~2011-05-15 12:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-13 10:10 qt-x11-free_7.7.2 fail configure missing qmake Søren Holm
2011-05-13 13:19 ` Simon Busch
2011-05-13 14:43   ` Søren Holm
2011-05-13 19:02     ` Simon Busch
2011-05-13 14:28 ` Eivind Kvedalen
2011-05-13 15:46   ` Eric Bénard
2011-05-13 19:35     ` Eric Bénard
2011-05-14  0:36       ` Søren Holm
2011-05-15 12:06       ` Simon Busch
2011-05-15 12:07         ` [PATCH] qt4-native: build and install all needed qt4 tools Simon Busch
2011-05-15 12:15         ` Simon Busch [this message]

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=4DCFC3C4.506@gravedo.de \
    --to=morphis@gravedo.de \
    --cc=openembedded-devel@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.