From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: openembedded-commits@lists.openembedded.org
Subject: Re: [oe-commits] Paul Eggleton : qt4: allow recipes building commercial edition
Date: Sun, 5 Aug 2012 15:16:15 +0200 [thread overview]
Message-ID: <20120805131615.GC3267@jama.jama.net> (raw)
In-Reply-To: <20120803071730.GA30148@jama.jama.net>
[-- Attachment #1: Type: text/plain, Size: 3024 bytes --]
On Fri, Aug 03, 2012 at 09:17:30AM +0200, Martin Jansa wrote:
> On Fri, Aug 03, 2012 at 12:15:26AM +0200, Martin Jansa wrote:
> > On Tue, Jul 31, 2012 at 07:05:17AM +0000, git@git.openembedded.org wrote:
> > > Module: openembedded-core.git
> > > Branch: master
> > > Commit: 2be0058fc4acddab611637656183accd052b40eb
> > > URL: http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=2be0058fc4acddab611637656183accd052b40eb
> > >
> > > Author: Paul Eggleton <paul.eggleton@linux.intel.com>
> > > Date: Tue Jul 31 00:31:00 2012 +0100
> > >
> > > qt4: allow recipes building commercial edition
> > >
> > > To enable building the commercial edition of Qt (through additional
> > > recipes that are *not* provided by OE-Core) we need to tweak a few
> > > things:
> > >
> > > * Don't make recipes that inherit qt4x11.bbclass depend on qt4-x11-free
> > > - instead add qt4-x11 to DEPENDS and then have qt4-x11-free include
> > > this in its PROVIDES. A commercial equivalent recipe should do the
> > > same.
> > > * Add a QT_LICENSE_FILE variable that can be used to specify the license
> > > file required by the commercial edition.
> > > * Add a QT_LICENSE_FLAGS variable which the recipe can set to select the
> > > license option being used. The default of "-opensource" retains the
> > > current behaviour; a commercial recipe should set it to "-commercial".
> > >
> > > Fixes [YOCTO #2505].
> > >
> > > Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
> > > Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> >
> > After this patch I see, libdummy.prl created again
> > OE @ ~/projects/shr-chroot $ ll include/WebCore/libdummy.prl
> > -rw-r--r-- 1 bitbake bitbake 651 Aug 2 19:23 include/WebCore/libdummy.prl
> >
> > originally fixed by:
> > http://git.openembedded.org/openembedded-core/commit/?id=7d3fd68480d54a8ef0d91a772df3506cd45ef2c2
> >
> > Do you have any idea why it's broken again? If you still have log.do_configure logs, can you check for
> > WARNING: DESTDIR: Cannot access directory '/include/WebCore'
> > ?
> >
> > Cheers,
>
Ah, this isn't from qt4-x11-free, only that /include/WebCore should be,
but I've tried to reproduce it again and even after rebuilding
qt4-x11-free, qt4-x11-embedded, qt-mobility-embedded, qt-mobility-x11
it's not created now.
Will try for different arch, because last time I've seen it also only
for arm* and not x86 (which I was rebuilding now).
Cheers,
> Hmm even more this time:
> ISIS_OUT/
> ISIS_OUT/include
> ISIS_OUT/include/webkit
> ISIS_OUT/include/webkit/npapi
> ISIS_OUT/include/webkit/npapi/nptypes.h
> ISIS_OUT/include/webkit/npapi/npapi.h
> ISIS_OUT/include/webkit/npapi/npupp.h
> ISIS_OUT/include/webkit/npapi/npruntime.h
>
> Created in dir one level above dir from where bitbake was started.
>
> --
> Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2012-08-05 13:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120731070518.61E5C10217@opal>
2012-08-02 22:15 ` [oe-commits] Paul Eggleton : qt4: allow recipes building commercial edition Martin Jansa
2012-08-03 7:17 ` Martin Jansa
2012-08-05 13:16 ` Martin Jansa [this message]
2012-08-05 13:50 ` [PATCH] qt4-native: fix creating /include directory in build host root Martin Jansa
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=20120805131615.GC3267@jama.jama.net \
--to=martin.jansa@gmail.com \
--cc=openembedded-commits@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox