All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-qt5] Antisocial layer behaviour
Date: Mon, 31 Mar 2014 14:17:39 +0200	[thread overview]
Message-ID: <20140331121739.GE2425@jama> (raw)
In-Reply-To: <1396267345.14790.70.camel@ted>

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

On Mon, Mar 31, 2014 at 01:02:25PM +0100, Richard Purdie wrote:
> I noticed some rebuilds happening when my cache should have been good.
> "bitbake xxxx -S printdiff" showed:
> 
> Task cmake-native:do_configure couldn't be used from the cache because:
>   We need hash f8a8910df42f4330ddaf9e40105baa7d, closest matching task was 93ac4b3cc3e9b5dd0868377cf287ca3d
>   basehash changed from 6b93d63cb19070822b91834c3ec58922 to a805733675f04ac021199aa92ed54cb5
>   Variable do_configure value changed from '    sed -i 's/^find_package(Qt5Core QUIET)$/#find_package(Qt5Core QUIET)/g' ${S}/Tests/RunCMake/CMakeLists.txt
>     sed -i 's/^find_package(Qt5Core REQUIRED)/#find_package(Qt5Core REQUIRED)/g' ${S}/Tests/RunCMake/IncompatibleQt/IncompatibleQt.cmake
>     sed -i 's/^  find_package(Qt5Widgets REQUIRED)/#  find_package(Qt5Widgets REQUIRED)/g' ${S}/Tests/QtAutomoc/CMakeLists.txt
>     sed -i 's/^find_package(Qt5Core REQUIRED)/#find_package(Qt5Core REQUIRED)/g' ${S}/Tests/Qt4And5Automoc/CMakeLists.txt
>     sed -i 's/^  find_package(Qt5Widgets QUIET NO_MODULE)/#  find_package(Qt5Widgets QUIET NO_MODULE)/g' ${S}/Tests/CMakeLists.txt
>     sed -i 's/^find_package(Qt5Widgets QUIET)/#find_package(Qt5Widgets QUIET)/g' ${S}/Source/QtDialog/CMakeLists.txt
> 	./configure --prefix=${prefix}
> ' to '	./configure --prefix=${prefix}
> '
> 
> so basically the bbappend in meta-qt5 means that everything using
> cmake-native will get rebuilt unless you either include or exclude the
> layer everywhere :(

Well it's fixing the issue which happens only when you're including
meta-qt5 and have qtbase(-native) installed in sysroot, that's why it
was fixed by .bbappend.

> Can we try and find a better way to work around whatever that bbappend
> is trying to fix please?

I have patch to move this hack to oe-core recipe, but it's still hack
I'm not very proud of.

Should I send it?

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

      reply	other threads:[~2014-03-31 12:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-31 12:02 [meta-qt5] Antisocial layer behaviour Richard Purdie
2014-03-31 12:17 ` Martin Jansa [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=20140331121739.GE2425@jama \
    --to=martin.jansa@gmail.com \
    --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.