* Re: [PATCH 0/2] Upgrade libfm/pcmanfm
From: Saul Wold @ 2011-10-14 16:39 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <cover.1318385789.git.edwin.zhai@intel.com>
On 10/11/2011 07:20 PM, edwin.zhai@intel.com wrote:
> From: Zhai Edwin<edwin.zhai@intel.com>
>
> All,
> These 2 patches upgrade libfm and pcmanfm. Pls. help to review and pull.
>
> Thanks,
> Edwin
>
> The following changes since commit 0d8c8cf462e5df446669355b554b3d5fdc532a11:
>
> mutter: update to 2.29.1 and fix SRC_URI (2011-10-07 11:35:50 +0100)
>
> are available in the git repository at:
> git://git.pokylinux.org/poky-contrib gzhai/master2
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=gzhai/master2
>
> Zhai Edwin (2):
> libfm: Upgrade to 0.1.16
> pcmanfm: Upgrade to 0.9.9
>
> .../pcmanfm/files/owl-window-menu.patch | 53 ++++++++++----------
> .../pcmanfm/{pcmanfm_0.9.8.bb => pcmanfm_0.9.9.bb} | 6 +-
> .../libfm/libfm-0.1.14/use_deprecate_func.patch | 13 -----
> .../libfm/libfm-0.1.16/configure_fix.patch | 19 +++++++
> .../libfm/{libfm_0.1.14.bb => libfm_0.1.16.bb} | 8 ++--
> 5 files changed, 52 insertions(+), 47 deletions(-)
> rename meta/recipes-sato/pcmanfm/{pcmanfm_0.9.8.bb => pcmanfm_0.9.9.bb} (87%)
> delete mode 100644 meta/recipes-support/libfm/libfm-0.1.14/use_deprecate_func.patch
> create mode 100644 meta/recipes-support/libfm/libfm-0.1.16/configure_fix.patch
> rename meta/recipes-support/libfm/{libfm_0.1.14.bb => libfm_0.1.16.bb} (73%)
>
Merged into OE-Core
Thanks
Sau!
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
^ permalink raw reply
* Re: [PATCH 0/1] distro_tracking_fields.inc: Add maintainer for some packages without maintainer
From: Saul Wold @ 2011-10-14 16:35 UTC (permalink / raw)
To: Xiaofeng Yan; +Cc: openembedded-core
In-Reply-To: <cover.1318318965.git.xiaofeng.yan@windriver.com>
On 10/11/2011 01:51 AM, Xiaofeng Yan wrote:
> From: Xiaofeng Yan<xiaofeng.yan@windriver.com>
>
> Add maintainer's name for the following packages:
> bind
> libx11-diet
> qmmp
> libarchive
> xserver-kdrive
> xserver-xf86-lite
> directfb
>
> Pull URL: git://git.pokylinux.org/poky-contrib.git
> Branch: xiaofeng/maintainer
> Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=xiaofeng/maintainer
>
> Thanks,
> Xiaofeng Yan<xiaofeng.yan@windriver.com>
> ---
>
>
> Xiaofeng Yan (1):
> distro_tracking_fields.inc: Add maintainer for some packages without
> maintainer
>
> .../conf/distro/include/distro_tracking_fields.inc | 15 +++++++++++++++
> 1 files changed, 15 insertions(+), 0 deletions(-)
>
>
Merged into OE-Core.
Please send any corrected updates for this file, I think I may have
merged the older version.
Thanks
Sau!
^ permalink raw reply
* Re: [PATCH] bluez4: Add ending quote of FILES_${PN}-dbg
From: Saul Wold @ 2011-10-14 16:33 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <1318312278-24520-1-git-send-email-noor_ahsan@mentor.com>
On 10/10/2011 10:51 PM, Noor, Ahsan wrote:
> From: Noor Ahsan<noor_ahsan@mentor.com>
>
> * .debug directory was being moved in bluez4 package. Although we have asked to move it in bluez4-dbg package but as FILES_${PN}-dbg was not having ending quote, .debug folder was not being moved to correct directory in packages-split.
>
> Signed-off-by: Noor Ahsan<noor_ahsan@mentor.com>
> ---
> meta/recipes-connectivity/bluez/bluez4_4.96.bb | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/meta/recipes-connectivity/bluez/bluez4_4.96.bb b/meta/recipes-connectivity/bluez/bluez4_4.96.bb
> index 5c170c1..420a525 100644
> --- a/meta/recipes-connectivity/bluez/bluez4_4.96.bb
> +++ b/meta/recipes-connectivity/bluez/bluez4_4.96.bb
> @@ -30,4 +30,4 @@ FILES_${PN}-dbg += "\
> ${libdir}/bluetooth/plugins/.debug \
> ${libdir}/*/.debug \
> ${base_libdir}/udev/.debug \
> -
> + "
Merged into OE-Core
Thanks
Sau!
^ permalink raw reply
* Re: [PATCH 0/1] QEMU 0.15 update please test
From: Saul Wold @ 2011-10-14 16:32 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <cover.1317843784.git.raj.khem@gmail.com>
On 10/05/2011 12:45 PM, Khem Raj wrote:
> This brings in qemu-0.15 into OE-core I have had limited testing
> on it and mainly on qemuarm. Please help testing it on other architectures
> I will also work on getting it more solidified and bring some backports
> as needed.
>
> The following changes since commit abde9f65b1617ec61e964c4b3502fd4ad2215dcf:
>
> shared-mime-info: Upgrade recipes from 0.90 -> 0.91 (2011-10-05 12:39:47 -0700)
>
> are available in the git repository at:
> git://git.openembedded.org/openembedded-core-contrib kraj/qemu-update
> http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=kraj/qemu-update
>
> Khem Raj (1):
> qemu-0.15: Add recipe and forward port patches from 0.14
>
> .../qemu/qemu-0.15.0/arm-bgr.patch | 30 +
> .../qemu/qemu-0.15.0/enable-i386-linux-user.patch | 55 +
> .../fallback-to-safe-mmap_min_addr.patch | 39 +
> .../qemu/qemu-0.15.0/fix-configure-checks.patch | 22 +
> .../qemu/qemu-0.15.0/fix-nogl.patch | 127 +
> .../qemu/qemu-0.15.0/glflags.patch | 15 +
> .../qemu/qemu-0.15.0/init-info.patch | 18 +
> .../qemu/qemu-0.15.0/larger_default_ram_size.patch | 22 +
> .../qemu/qemu-0.15.0/linker-flags.patch | 25 +
> .../qemu/qemu-0.15.0/no-strip.patch | 15 +
> .../qemu/qemu-0.15.0/opengl-sdl-fix.patch | 43 +
> .../qemu/qemu-0.15.0/powerpc_rom.bin | Bin 0 -> 4096 bytes
> .../qemu/qemu-0.15.0/qemu-git-qemugl-host.patch |34368 ++++++++++++++++++++
> .../qemu/qemu-0.15.0/qemu-vmware-vga-depth.patch | 118 +
> .../qemugl-allow-glxcontext-release.patch | 65 +
> .../qemu/qemu-0.15.0/qemugl-fix.patch | 74 +
> meta/recipes-devtools/qemu/qemu_0.15.0.bb | 45 +
> 17 files changed, 35081 insertions(+), 0 deletions(-)
> create mode 100644 meta/recipes-devtools/qemu/qemu-0.15.0/arm-bgr.patch
> create mode 100644 meta/recipes-devtools/qemu/qemu-0.15.0/enable-i386-linux-user.patch
> create mode 100644 meta/recipes-devtools/qemu/qemu-0.15.0/fallback-to-safe-mmap_min_addr.patch
> create mode 100644 meta/recipes-devtools/qemu/qemu-0.15.0/fix-configure-checks.patch
> create mode 100644 meta/recipes-devtools/qemu/qemu-0.15.0/fix-nogl.patch
> create mode 100644 meta/recipes-devtools/qemu/qemu-0.15.0/glflags.patch
> create mode 100644 meta/recipes-devtools/qemu/qemu-0.15.0/init-info.patch
> create mode 100644 meta/recipes-devtools/qemu/qemu-0.15.0/larger_default_ram_size.patch
> create mode 100644 meta/recipes-devtools/qemu/qemu-0.15.0/linker-flags.patch
> create mode 100644 meta/recipes-devtools/qemu/qemu-0.15.0/no-strip.patch
> create mode 100644 meta/recipes-devtools/qemu/qemu-0.15.0/opengl-sdl-fix.patch
> create mode 100644 meta/recipes-devtools/qemu/qemu-0.15.0/powerpc_rom.bin
> create mode 100644 meta/recipes-devtools/qemu/qemu-0.15.0/qemu-git-qemugl-host.patch
> create mode 100644 meta/recipes-devtools/qemu/qemu-0.15.0/qemu-vmware-vga-depth.patch
> create mode 100644 meta/recipes-devtools/qemu/qemu-0.15.0/qemugl-allow-glxcontext-release.patch
> create mode 100644 meta/recipes-devtools/qemu/qemu-0.15.0/qemugl-fix.patch
> create mode 100644 meta/recipes-devtools/qemu/qemu_0.15.0.bb
>
Merged into OE-Core
I needed to add an additional patch to add glib-2.0-native to the
qemu-native depends
We will remove qemu-0.14 after we get through a QA cycle.
Thanks
Sau!
^ permalink raw reply
* Re: [PATCH 0/2] Minor autoconf & autotools.bbclass fixes (supercedes previous misc fixes request)
From: Saul Wold @ 2011-10-14 16:30 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <cover.1318281075.git.kergoth@gmail.com>
On 10/10/2011 02:13 PM, Christopher Larson wrote:
> The following changes since commit 4732222c46652951e66aae377631f4a361179d8f:
>
> Fix sysprof for powerpc64 (2011-10-10 09:54:03 +0100)
>
> are available in the git repository at:
> http://github.com/kergoth/oe-core misc-fixes
>
> Christopher Larson (2):
> autotools: fix multi-word arguments for EXTRA_OECONF
> autoconf: no need to hardcode the full path to m4
>
> meta/classes/autotools.bbclass | 6 ++----
> meta/recipes-devtools/autoconf/autoconf_2.68.bb | 4 +++-
> 2 files changed, 5 insertions(+), 5 deletions(-)
>
Merged into OE-Core
Thanks
Sau!
^ permalink raw reply
* Re: [PATCH] farsight2, ldconfig-native, gnutls: There is no GPLv2.1, correct the fields
From: Saul Wold @ 2011-10-14 16:30 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <1318009017-6186-1-git-send-email-raj.khem@gmail.com>
On 10/07/2011 10:36 AM, Khem Raj wrote:
> The licenses were either LGPLv2.1 or GPLv2
> make the changes appropriately
>
> Signed-off-by: Khem Raj<raj.khem@gmail.com>
> ---
> .../farsight/farsight2_0.0.9.bb | 4 ++--
> meta/recipes-core/eglibc/ldconfig-native_2.12.1.bb | 4 ++--
> meta/recipes-support/gnutls/gnutls.inc | 4 ++--
> 3 files changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/meta-demoapps/recipes-connectivity/farsight/farsight2_0.0.9.bb b/meta-demoapps/recipes-connectivity/farsight/farsight2_0.0.9.bb
> index a7bdc97..ee0ce8a 100644
> --- a/meta-demoapps/recipes-connectivity/farsight/farsight2_0.0.9.bb
> +++ b/meta-demoapps/recipes-connectivity/farsight/farsight2_0.0.9.bb
> @@ -1,12 +1,12 @@
> DESCRIPTION = "FarSight is an audio/video conferencing framework specifically designed for Instant Messengers."
> HOMEPAGE = "http://farsight.sf.net"
> SRC_URI = "http://farsight.freedesktop.org/releases/farsight2/${BPN}-${PV}.tar.gz"
> -LICENSE = "GPLv2.1"
> +LICENSE = "LGPLv2.1"
> DEPENDS = "libnice glib-2.0 libxml2 zlib dbus gstreamer gst-plugins-base"
>
> inherit autotools
>
> -PR = "r1"
> +PR = "r2"
>
> EXTRA_OECONF = " \
> --disable-debug \
> diff --git a/meta/recipes-core/eglibc/ldconfig-native_2.12.1.bb b/meta/recipes-core/eglibc/ldconfig-native_2.12.1.bb
> index 00edb6e..2a93913 100644
> --- a/meta/recipes-core/eglibc/ldconfig-native_2.12.1.bb
> +++ b/meta/recipes-core/eglibc/ldconfig-native_2.12.1.bb
> @@ -1,6 +1,6 @@
> DESCRIPTION = "A standalone native ldconfig build"
>
> -LICENSE = "GPLv2.1"
> +LICENSE = "GPLv2+"
>
> LIC_FILES_CHKSUM = "file://${S}/ldconfig.c;endline=17;md5=1d15f20937c055cb5de2329a4c054399"
>
> @@ -12,7 +12,7 @@ SRC_URI = "file://ldconfig-native-2.12.1.tar.bz2 \
> file://flag_fix.patch \
> file://endianess-header.patch"
>
> -PR = "r1"
> +PR = "r2"
>
> inherit native
>
> diff --git a/meta/recipes-support/gnutls/gnutls.inc b/meta/recipes-support/gnutls/gnutls.inc
> index 9257880..d73c799 100644
> --- a/meta/recipes-support/gnutls/gnutls.inc
> +++ b/meta/recipes-support/gnutls/gnutls.inc
> @@ -3,11 +3,11 @@ HOMEPAGE = "http://www.gnu.org/software/gnutls/"
> BUGTRACKER = "https://savannah.gnu.org/support/?group=gnutls"
> DEPENDS = "zlib lzo libtasn1 libgcrypt (>= 1.4.2) libcap"
>
> -INC_PR = "r2"
> +INC_PR = "r3"
>
> LICENSE = "GPLv3+& LGPLv2.1+"
> LICENSE_${PN} = "LGPLv2.1+"
> -LICENSE_${PN}-xx = "GPLv2.1+"
> +LICENSE_${PN}-xx = "LGPLv2.1+"
> LICENSE_${PN}-bin = "GPLv3+"
> LICENSE_${PN}-extra = "GPLv3+"
> LICENSE_${PN}-openssl = "GPLv3+"
Merged into OE-Core
Thanks
Sau!
^ permalink raw reply
* Re: [PATCH] qt4: Added support for QtMobility 1.2
From: Koen Kooi @ 2011-10-14 16:28 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <4E986233.8020505@linux.intel.com>
Op 14 okt. 2011, om 18:24 heeft Saul Wold het volgende geschreven:
> On 10/14/2011 08:18 AM, Dmitry Cherukhin wrote:
>> On Mon, 2011-09-26 at 16:32 -0700, Saul Wold wrote:
>>> On 09/23/2011 07:13 AM, Dmitry Cherukhin wrote:
>>>> This patch is indented to add new functionality,
>>>> specifically, the patch adds support for
>>>> the QtMobility 1.2 package.
>>>>
>>>> Added two recipes:
>>>> 1) qt-mobility-x11 builds the QtMobility 1.2 package
>>>> on the basis of qt4-x11-free;
>>>> 2) qt-mobility-embedded builds the QtMobility 1.2 package
>>>> on the basis of qt4-embedded.
>>>>
>>>> Signed-off-by: Dmitry Cherukhin<dima_ch@emcraft.com>
>>>> ---
>>>> meta/recipes-qt/qt4/files/qtm_qtmobility_pro.patch | 28 +++++++++++
>>>> meta/recipes-qt/qt4/files/qtme_gstreamer_pro.patch | 16 ++++++
>>>> meta/recipes-qt/qt4/qt-mobility-embedded_1.2.0.bb | 13 +++++
>>>> meta/recipes-qt/qt4/qt-mobility-x11_1.2.0.bb | 11 ++++
>>>> meta/recipes-qt/qt4/qt-mobility_1.2.0.inc | 51 ++++++++++++++++++++
>>>> 5 files changed, 119 insertions(+), 0 deletions(-)
>>>> create mode 100644 meta/recipes-qt/qt4/files/qtm_qtmobility_pro.patch
>>>> create mode 100644 meta/recipes-qt/qt4/files/qtme_gstreamer_pro.patch
>>>> create mode 100644 meta/recipes-qt/qt4/qt-mobility-embedded_1.2.0.bb
>>>> create mode 100644 meta/recipes-qt/qt4/qt-mobility-x11_1.2.0.bb
>>>> create mode 100644 meta/recipes-qt/qt4/qt-mobility_1.2.0.inc
>>>>
>>>> diff --git a/meta/recipes-qt/qt4/files/qtm_qtmobility_pro.patch b/meta/recipes-qt/qt4/files/qtm_qtmobility_pro.patch
>>>> new file mode 100644
>>>> index 0000000..689c224
>>>> --- /dev/null
>>>> +++ b/meta/recipes-qt/qt4/files/qtm_qtmobility_pro.patch
>>>> @@ -0,0 +1,28 @@
>>>> +This patch fixes the following issue at the configure stage:
>>>> + Project ERROR: Qt Mobility requires Qt 4.6 or higher. Qt was found.
>>>> +The version of Qt is already 4.7.3, so this is misconfiguration problem.
>>>> +
>>>> +The origin of this patch is:
>>>> + http://neophysis.git.sourceforge.net/git/gitweb.cgi?p=neophysis/openembedded;
>>>> + a=blob;f=recipes/neophysis/qt-mobility-1.0.0/qtmobility_pro.patch;
>>>> + h=fc5e1691aed47bc50d87e5c33497354182cacda4;hb=refs/heads/neophysis-testing-0.3
>>>> +Upstream-Status: not-appropriate
>>>
>>> Please refer to wiki page on www.openembedded.org for the corrcet
>>> formating of the Upstream-Status field. You are also missing a
>>> Signed-off-by: line for each patch file.
>>>
>>> (I would give the exact page, but the site appears to be having problems)
>>>
>>
>> Thanks!
>> I removed all .patch files, new version of the patch is here:
>> http://thread.gmane.org/gmane.comp.handhelds.openembedded.core/8708
>>
> That's great, but that reader seems to mangle emails in a way that I can't use them for patching, it would be great if you could just send the v2 to this mailing list.
The reader is just a view into the mail archive, so if you scroll back 8 days in your oe-core folder, you should see the patch :)
^ permalink raw reply
* Re: [PATCH] qt4: Added support for QtMobility 1.2
From: Saul Wold @ 2011-10-14 16:24 UTC (permalink / raw)
To: dima_ch; +Cc: Patches and discussions about the oe-core layer
In-Reply-To: <1318605488.23340.580.camel@vladimir.emcraft.com>
On 10/14/2011 08:18 AM, Dmitry Cherukhin wrote:
> On Mon, 2011-09-26 at 16:32 -0700, Saul Wold wrote:
>> On 09/23/2011 07:13 AM, Dmitry Cherukhin wrote:
>>> This patch is indented to add new functionality,
>>> specifically, the patch adds support for
>>> the QtMobility 1.2 package.
>>>
>>> Added two recipes:
>>> 1) qt-mobility-x11 builds the QtMobility 1.2 package
>>> on the basis of qt4-x11-free;
>>> 2) qt-mobility-embedded builds the QtMobility 1.2 package
>>> on the basis of qt4-embedded.
>>>
>>> Signed-off-by: Dmitry Cherukhin<dima_ch@emcraft.com>
>>> ---
>>> meta/recipes-qt/qt4/files/qtm_qtmobility_pro.patch | 28 +++++++++++
>>> meta/recipes-qt/qt4/files/qtme_gstreamer_pro.patch | 16 ++++++
>>> meta/recipes-qt/qt4/qt-mobility-embedded_1.2.0.bb | 13 +++++
>>> meta/recipes-qt/qt4/qt-mobility-x11_1.2.0.bb | 11 ++++
>>> meta/recipes-qt/qt4/qt-mobility_1.2.0.inc | 51 ++++++++++++++++++++
>>> 5 files changed, 119 insertions(+), 0 deletions(-)
>>> create mode 100644 meta/recipes-qt/qt4/files/qtm_qtmobility_pro.patch
>>> create mode 100644 meta/recipes-qt/qt4/files/qtme_gstreamer_pro.patch
>>> create mode 100644 meta/recipes-qt/qt4/qt-mobility-embedded_1.2.0.bb
>>> create mode 100644 meta/recipes-qt/qt4/qt-mobility-x11_1.2.0.bb
>>> create mode 100644 meta/recipes-qt/qt4/qt-mobility_1.2.0.inc
>>>
>>> diff --git a/meta/recipes-qt/qt4/files/qtm_qtmobility_pro.patch b/meta/recipes-qt/qt4/files/qtm_qtmobility_pro.patch
>>> new file mode 100644
>>> index 0000000..689c224
>>> --- /dev/null
>>> +++ b/meta/recipes-qt/qt4/files/qtm_qtmobility_pro.patch
>>> @@ -0,0 +1,28 @@
>>> +This patch fixes the following issue at the configure stage:
>>> + Project ERROR: Qt Mobility requires Qt 4.6 or higher. Qt was found.
>>> +The version of Qt is already 4.7.3, so this is misconfiguration problem.
>>> +
>>> +The origin of this patch is:
>>> + http://neophysis.git.sourceforge.net/git/gitweb.cgi?p=neophysis/openembedded;
>>> + a=blob;f=recipes/neophysis/qt-mobility-1.0.0/qtmobility_pro.patch;
>>> + h=fc5e1691aed47bc50d87e5c33497354182cacda4;hb=refs/heads/neophysis-testing-0.3
>>> +Upstream-Status: not-appropriate
>>
>> Please refer to wiki page on www.openembedded.org for the corrcet
>> formating of the Upstream-Status field. You are also missing a
>> Signed-off-by: line for each patch file.
>>
>> (I would give the exact page, but the site appears to be having problems)
>>
>
> Thanks!
> I removed all .patch files, new version of the patch is here:
> http://thread.gmane.org/gmane.comp.handhelds.openembedded.core/8708
>
That's great, but that reader seems to mangle emails in a way that I
can't use them for patching, it would be great if you could just send
the v2 to this mailing list.
Thanks
Sau!
> Dima
>
>
^ permalink raw reply
* Re: [PATCH] mesa-dri: Enable swrast only by default and intel drivers only on IA platform
From: Martin Jansa @ 2011-10-14 16:05 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <1318607759.2342.28.camel@ted>
[-- Attachment #1: Type: text/plain, Size: 1310 bytes --]
On Fri, Oct 14, 2011 at 04:55:50PM +0100, Richard Purdie wrote:
> On Fri, 2011-10-14 at 17:30 +0200, Martin Jansa wrote:
> > On Fri, Oct 14, 2011 at 04:25:16PM +0100, Richard Purdie wrote:
> > > On Fri, 2011-10-14 at 11:46 -0300, Otavio Salvador wrote:
> > > > +1
> > > >
> > > > Just another thing, I'd prefer to have DRIDRIVERS as ?= so machine can
> > > > override it.
> > >
> > > I really wouldn't recommend overriding this on a per machine basis, it
> > > needs to be on a per arch basis. This is because the recipe is not
> > > machine specific (nor should it be).
> > >
> > > Configuration therefore falls to the distro, not machine.
> >
> > Why not make it machine specific only when machine provides own module
> > (like the case with glamo on om-gta02)?
> >
> > Or recipe cannot change PACKAGE_ARCH in some special cases (like
> > $MACHINE in path to some file in SRC_URI) anymore?
>
> It works just fine but its not nice practise in my opinion for a library
> like this and I don't see there is any need in this case. Certainly I
> don't see it as something OE-Core should be recommending.
So can I send patches adding my glamo.patch to libdrm and mesa-dri so we
can add glamo to
DRIDRIVERS_armv4t ?
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
^ permalink raw reply
* Re: [oe-core 14/20] mesa-dri: introduce MACHINE_DRI_MODULES
From: Richard Purdie @ 2011-10-14 16:04 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <20111013140718.GD28525@jama.jama.net>
On Thu, 2011-10-13 at 16:07 +0200, Martin Jansa wrote:
> On Thu, Oct 13, 2011 at 02:56:24PM +0100, Richard Purdie wrote:
> > On Thu, 2011-10-13 at 15:32 +0200, Martin Jansa wrote:
> > > On Thu, Oct 13, 2011 at 02:23:54PM +0100, Richard Purdie wrote:
> > > > On Thu, 2011-10-13 at 13:30 +0200, Martin Jansa wrote:
> > > > > * not everybody needs i915, i965
> > > > >
> > > > > Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> > > > > ---
> > > > > meta/recipes-graphics/mesa/mesa-dri.inc | 4 ++++
> > > > > meta/recipes-graphics/mesa/mesa-dri_7.11.bb | 2 --
> > > > > 2 files changed, 4 insertions(+), 2 deletions(-)
> > > > >
> > > > > diff --git a/meta/recipes-graphics/mesa/mesa-dri.inc b/meta/recipes-graphics/mesa/mesa-dri.inc
> > > > > index 603438e..be6905c 100644
> > > > > --- a/meta/recipes-graphics/mesa/mesa-dri.inc
> > > > > +++ b/meta/recipes-graphics/mesa/mesa-dri.inc
> > > > > @@ -6,6 +6,10 @@ DEFAULT_PREFERENCE = "-1"
> > > > >
> > > > > EXTRA_OECONF += "--with-driver=dri --disable-egl --disable-gallium --without-gallium-drivers"
> > > > >
> > > > > +MACHINE_DRI_MODULES ?= ""
> > > > > +PACKAGE_ARCH = "${@['${MACHINE_ARCH}','${TUNE_PKGARCH}'][bb.data.getVar('MACHINE_DRI_MODULES',d,1) == '']}"
> > > > > +EXTRA_OECONF += "--with-dri-drivers=swrast,${MACHINE_DRI_MODULES}"
> > > > > +
> > > > > python populate_packages_prepend() {
> > > > > import os.path
> > > >
> > > > Whilst I understand the problem, I don't like this solution.
> > > > Particularly, it means that the meas-dri package needs to be marked as
> > > > machine specific which I don't like the idea of at all.
> > > >
> > > > How about we do this on a per architecture basis?
> > >
> > > taken from cover-letter:
> > > but maybe we can use it as distro variable and keep it with default arch.
> > > But then we cannot just add ie glamo dri module from meta-openmoko like this:
> > > http://git.shr-project.org/git/?p=meta-smartphone.git;a=commit;h=b50c8d00cf764c276b0792c0623b8eda3d18d343
> > > without distro (setting MACHINE_DRI_MODULES) depending on such bsp layer.
> >
> > Whilst I hadn't seen the patch I was guessing you were doing something
> > like this. Will the glamo module build on all arm platforms or just
> > gta02 specifically?
>
> It should build on all arm platforms, but depends on another patch to
> libdrm
> http://git.shr-project.org/git/?p=meta-smartphone.git;a=commit;h=0a846fa3dec896751b44811cd909013874920aae
> which should also build on all arm platforms.
>
> I was using both patches for all machines (distr==SHR basis) in OE-classic,
> but with BSP layers I found it nice to keep them only in respective layer
> and now I would need to move them to upper layer again..
Not necessarily, you can keep them in the layer but apply the patch
globally. This means you do need to build shr with all layers enabled
but that shouldn't be too much of an issue?
Cheers,
Richard
^ permalink raw reply
* Re: [PATCH] arch-powerpc: set PACKAGE_EXTRA_ARCHS
From: Mark Hatle @ 2011-10-14 15:56 UTC (permalink / raw)
To: openembedded-core
In-Reply-To: <4E973C99.4080402@emcraft.com>
On 10/13/11 2:31 PM, Ilya Yanok wrote:
> Hi guys,
>
> any comments on this patch?
>
> Regards, Ilya.
>
> On 07.09.2011 19:38, Ilya Yanok wrote:
>> Set PACKAGE_EXTRA_ARCHS for the generic tunes ("powerpc" and
>> "powerpc-nf") thus allowing to use them instead of tuning to the
>> specific CPU.
>>
>> Signed-off-by: Ilya Yanok <yanok@emcraft.com>
>> ---
>> meta/conf/machine/include/powerpc/arch-powerpc.inc | 6 ++++--
>> meta/conf/machine/include/tune-ppc603e.inc | 2 +-
>> meta/conf/machine/include/tune-ppce300c2.inc | 2 +-
>> meta/conf/machine/include/tune-ppce500mc.inc | 2 +-
>> 4 files changed, 7 insertions(+), 5 deletions(-)
>>
>> diff --git a/meta/conf/machine/include/powerpc/arch-powerpc.inc b/meta/conf/machine/include/powerpc/arch-powerpc.inc
>> index da1a1d6..8347f86 100644
>> --- a/meta/conf/machine/include/powerpc/arch-powerpc.inc
>> +++ b/meta/conf/machine/include/powerpc/arch-powerpc.inc
>> @@ -25,9 +25,11 @@ TUNE_PKGARCH ?= "${PPCPKGARCH}"
>>
>> # Basic tune definitions
>> AVAILTUNES += "powerpc powerpc-nf"
>> -TUNE_FEATURES_tune-powerpc ?= "m32 fpu-hard"
>> -BASE_LIB_tune-powerpc = "lib"
>> TUNE_FEATURES_tune-powerpc-nf ?= "m32 fpu-soft"
>> BASE_LIB_tune-powerpc-nf = "lib"
>> +PACKAGE_EXTRA_ARCHS_tune-powerpc-nf = "powerpc-nf"
>> +TUNE_FEATURES_tune-powerpc ?= "m32 fpu-hard"
>> +BASE_LIB_tune-powerpc = "lib"
>> +PACKAGE_EXTRA_ARCHS_tune-powerpc = "${PACKAGE_EXTRA_ARCHS_tune-powerpc-nf} powerpc"
Usually we try to match the order of the AVAILTUNES, it just makes it easier to
look at, has no real technical consideration. So I'd change the order of what
you have above.
The last line thought is wrong. powerpc-nf and powerpc are not compatible with
each other. You can't list them both in the same EXTRA_ARCHS, as that indicates
to the package feed a compatible set of packaging ABIs.
This is a place that people familiar with ARM architectures often get confused
on PowerPC. The two ABIs often times can run together with limited problems,
but there WILL be problems as register passing and context switching
(setjmp/longjmp) are defined differently in the two ABIs.
So based on that, it appears to me that the only thing missing is:
PACKAGE_EXTRA_ARCHS_tune-powerpc-nf = "powerpc-nf"
Which I thought was automatic if the tune selected with powerpc-nf.
>>
>> diff --git a/meta/conf/machine/include/tune-ppc603e.inc b/meta/conf/machine/include/tune-ppc603e.inc
>> index c743dde..663f220 100644
>> --- a/meta/conf/machine/include/tune-ppc603e.inc
>> +++ b/meta/conf/machine/include/tune-ppc603e.inc
>> @@ -8,7 +8,7 @@ TUNE_PKGARCH = "${@bb.utils.contains('TUNE_FEATURES', 'ppc603e', 'ppc603e', '${P
>>
>> AVAILTUNES = "ppc603e"
>> TUNE_FEATURES_tune-ppc603e = "m32 fpu-hard ppc603e"
>> -PACKAGE_EXTRA_ARCHS_tune-ppc603e = "powerpc ppc603e"
>> +PACKAGE_EXTRA_ARCHS_tune-ppc603e = "${PACKAGE_EXTRA_ARCHS_tune-powerpc} ppc603e"
The above (assumine the previous comment on powerpc-nf) would result in the same
thing. This should be ok, but I'm not sure I see any advantage to doing it this
way.
>> # glibc configure options to get 603e specific library (for sqrt)
>> GLIBC_EXTRA_OECONF += "${@bb.utils.contains("TUNE_FEATURES", "ppc603e", "-with-cpu=603e", "", d)}"
>> diff --git a/meta/conf/machine/include/tune-ppce300c2.inc b/meta/conf/machine/include/tune-ppce300c2.inc
>> index 5eea4a6..bdca1aa 100644
>> --- a/meta/conf/machine/include/tune-ppce300c2.inc
>> +++ b/meta/conf/machine/include/tune-ppce300c2.inc
>> @@ -8,4 +8,4 @@ TUNE_PKGARCH = "${@bb.utils.contains("TUNE_FEATURES", "ppce300c2", "ppce300c2",
>>
>> AVAILTUNES += "ppce300c2"
>> TUNE_FEATURES_tune-ppce300c2 = "m32 fpu-soft ppce300c2"
>> -PACKAGE_EXTRA_ARCHS_tune-ppce300c2 = "powerpc-nf ppce300c2"
>> +PACKAGE_EXTRA_ARCHS_tune-ppce300c2 = "${PACKAGE_EXTRA_ARCHS_tune-powerpc-nf} ppce300c2"
Same as above...
>> diff --git a/meta/conf/machine/include/tune-ppce500mc.inc b/meta/conf/machine/include/tune-ppce500mc.inc
>> index 33820ef..950c46d 100644
>> --- a/meta/conf/machine/include/tune-ppce500mc.inc
>> +++ b/meta/conf/machine/include/tune-ppce500mc.inc
>> @@ -8,7 +8,7 @@ TUNE_PKGARCH = "${@bb.utils.contains("TUNE_FEATURES", "ppce500mc", "ppce500mc",
>>
>> AVAILTUNES = "ppce500mc"
>> TUNE_FEATURES_tune-ppce500mc = "m32 fpu-hard ppce500mc"
>> -PACKAGE_EXTRA_ARCHS_tune-ppce500mc = "powerpc ppce500mc"
>> +PACKAGE_EXTRA_ARCHS_tune-ppce500mc = "${PACKAGE_EXTRA_ARCHS_tune-powerpc} ppce500mc"
Same as above..
>> # glibc configure options to get e500mc specific library (for sqrt)
>> GLIBC_EXTRA_OECONF += "${@bb.utils.contains("TUNE_FEATURES", "ppce500mc", "-with-cpu=e500mc", "", d)}"
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
^ permalink raw reply
* Re: [PATCH] mesa-dri: Enable swrast only by default and intel drivers only on IA platform
From: Richard Purdie @ 2011-10-14 15:55 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <20111014153034.GL3542@jama.jama.net>
On Fri, 2011-10-14 at 17:30 +0200, Martin Jansa wrote:
> On Fri, Oct 14, 2011 at 04:25:16PM +0100, Richard Purdie wrote:
> > On Fri, 2011-10-14 at 11:46 -0300, Otavio Salvador wrote:
> > > +1
> > >
> > > Just another thing, I'd prefer to have DRIDRIVERS as ?= so machine can
> > > override it.
> >
> > I really wouldn't recommend overriding this on a per machine basis, it
> > needs to be on a per arch basis. This is because the recipe is not
> > machine specific (nor should it be).
> >
> > Configuration therefore falls to the distro, not machine.
>
> Why not make it machine specific only when machine provides own module
> (like the case with glamo on om-gta02)?
>
> Or recipe cannot change PACKAGE_ARCH in some special cases (like
> $MACHINE in path to some file in SRC_URI) anymore?
It works just fine but its not nice practise in my opinion for a library
like this and I don't see there is any need in this case. Certainly I
don't see it as something OE-Core should be recommending.
Cheers,
Richard
^ permalink raw reply
* Re: [PATCH] qt4: Added support for QtMobility 1.2
From: Dmitry Cherukhin @ 2011-10-14 15:14 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <AEDF5974-B8CC-4B58-ACDA-2E2808B22C40@dominion.thruhere.net>
On Wed, 2011-09-21 at 14:28 +0200, Koen Kooi wrote:
> Op 21 sep. 2011, om 14:19 heeft Dmitry Cherukhin het volgende geschreven:
>
> > Added two recipes:
> > 1) qt-mobility-x11 builds the QtMobility 1.2 package
> > on the basis of qt4-x11-free;
> > 2) qt-mobility-embedded builds the QtMobility 1.2 package
> > on the basis of qt4-embedded.
> >
> > Signed-off-by: Dmitry Cherukhin <dima_ch@emcraft.com>
> > ---
> > meta/recipes-qt/qt4/files/qtm_qtmobility_pro.patch | 19 ++++++++
> > .../qt4/files/qtme_connectivity_pro.patch | 12 +++++
> > meta/recipes-qt/qt4/files/qtme_gstreamer_pro.patch | 11 +++++
> > .../qt4/files/qtme_staticconfig_pri.patch | 18 ++++++++
> > .../qt4/files/qtmx_staticconfig_pri.patch | 10 ++++
>
> Could you please add patch headers to those patches describing what they intend to fix and what their upstream status is?
I removed all .patch files, new version of the patch is here:
http://thread.gmane.org/gmane.comp.handhelds.openembedded.core/8708
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
^ permalink raw reply
* Re: [PATCH] qt4: Added support for QtMobility 1.2
From: Dmitry Cherukhin @ 2011-10-14 15:14 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <CAP9ODKoWmECTvSMBiK-T=Wzch=+2bMQ7icS8KkzeOby_HQLxag@mail.gmail.com>
On Thu, 2011-09-22 at 10:24 -0300, Otavio Salvador wrote:
> On Thu, Sep 22, 2011 at 10:04, Dmitry Cherukhin <dima_ch@emcraft.com> wrote:
> ...
> > Upstream-Status: not-appropriate
> ...
>
> This and an explanation of the reasoning of each patch ought to be
> included into each .patch file that your commit is going to add.
>
I removed all .patch files, new version of the patch is here:
http://thread.gmane.org/gmane.comp.handhelds.openembedded.core/8708
^ permalink raw reply
* Re: [PATCH] mesa-dri: Enable swrast only by default and intel drivers only on IA platform
From: Koen Kooi @ 2011-10-14 15:40 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <20111014153034.GL3542@jama.jama.net>
Op 14 okt. 2011, om 17:30 heeft Martin Jansa het volgende geschreven:
> On Fri, Oct 14, 2011 at 04:25:16PM +0100, Richard Purdie wrote:
>> On Fri, 2011-10-14 at 11:46 -0300, Otavio Salvador wrote:
>>> +1
>>>
>>> Just another thing, I'd prefer to have DRIDRIVERS as ?= so machine can
>>> override it.
>>
>> I really wouldn't recommend overriding this on a per machine basis, it
>> needs to be on a per arch basis. This is because the recipe is not
>> machine specific (nor should it be).
>>
>> Configuration therefore falls to the distro, not machine.
>
> Why not make it machine specific only when machine provides own module
> (like the case with glamo on om-gta02)?
>
> Or recipe cannot change PACKAGE_ARCH in some special cases (like
> $MACHINE in path to some file in SRC_URI) anymore?
Kinda like the wpa-supplicant and mplayer trick in OE classic?
>
> Regards,
>
> --
> Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
^ permalink raw reply
* [v2 1/1] cmake : Disable building ccmake.
From: Philip Balister @ 2011-10-14 15:35 UTC (permalink / raw)
To: openembedded-core
ccmake fails to build due to an as-needed type error with -ltinfo. Disable
it for now since the build fails and cmake is what we need for target
sdk.
Signed-off-by: Philip Balister <philip@balister.org>
---
meta/recipes-devtools/cmake/cmake_2.8.5.bb | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/meta/recipes-devtools/cmake/cmake_2.8.5.bb b/meta/recipes-devtools/cmake/cmake_2.8.5.bb
index 4fa9562..8e04072 100644
--- a/meta/recipes-devtools/cmake/cmake_2.8.5.bb
+++ b/meta/recipes-devtools/cmake/cmake_2.8.5.bb
@@ -4,7 +4,7 @@ inherit cmake
DEPENDS += "curl expat zlib libarchive ncurses"
-PR = "${INC_PR}.2"
+PR = "${INC_PR}.3"
SRC_URI += "file://dont-run-cross-binaries.patch"
@@ -30,6 +30,7 @@ EXTRA_OECMAKE=" \
-DCMAKE_DOC_DIR=${docdir_stripped}/cmake-${CMAKE_MAJOR_VERSION} \
-DCMAKE_USE_SYSTEM_LIBRARIES=1 \
-DKWSYS_CHAR_IS_SIGNED=1 \
+ -DBUILD_CursesDialog=0 \
${@base_contains('DISTRO_FEATURES', 'largefile', '-DKWSYS_LFS_WORKS=1', '-DKWSYS_LFS_DISABLE=1', d)} \
"
--
1.7.3.4
^ permalink raw reply related
* Re: [PATCH] mesa-dri: Enable swrast only by default and intel drivers only on IA platform
From: Martin Jansa @ 2011-10-14 15:30 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <1318605925.2342.24.camel@ted>
[-- Attachment #1: Type: text/plain, Size: 797 bytes --]
On Fri, Oct 14, 2011 at 04:25:16PM +0100, Richard Purdie wrote:
> On Fri, 2011-10-14 at 11:46 -0300, Otavio Salvador wrote:
> > +1
> >
> > Just another thing, I'd prefer to have DRIDRIVERS as ?= so machine can
> > override it.
>
> I really wouldn't recommend overriding this on a per machine basis, it
> needs to be on a per arch basis. This is because the recipe is not
> machine specific (nor should it be).
>
> Configuration therefore falls to the distro, not machine.
Why not make it machine specific only when machine provides own module
(like the case with glamo on om-gta02)?
Or recipe cannot change PACKAGE_ARCH in some special cases (like
$MACHINE in path to some file in SRC_URI) anymore?
Regards,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
^ permalink raw reply
* Re: [PATCH] mesa-dri: Enable swrast only by default and intel drivers only on IA platform
From: Richard Purdie @ 2011-10-14 15:25 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <CAP9ODKod1GCk5gFPq0YkEPb0rZ3NHsD6YBu7cAQVDPLW0PN7xA@mail.gmail.com>
On Fri, 2011-10-14 at 11:46 -0300, Otavio Salvador wrote:
> +1
>
> Just another thing, I'd prefer to have DRIDRIVERS as ?= so machine can
> override it.
I really wouldn't recommend overriding this on a per machine basis, it
needs to be on a per arch basis. This is because the recipe is not
machine specific (nor should it be).
Configuration therefore falls to the distro, not machine.
Cheers,
Richard
^ permalink raw reply
* Re: [PATCH] qt4: Added support for QtMobility 1.2
From: Dmitry Cherukhin @ 2011-10-14 15:24 UTC (permalink / raw)
To: Paul Eggleton; +Cc: openembedded-core
In-Reply-To: <201109281521.07861.paul.eggleton@linux.intel.com>
On Wed, 2011-09-28 at 15:21 +0100, Paul Eggleton wrote:
> On Wednesday 28 September 2011 10:35:59 Dmitry Cherukhin wrote:
> > The QtMobility is a Qt add-on which allows to include standard mobile
> > functionality to Qt applications. For details, see
> > http://qt.nokia.com/products/qt-addons/mobility/
> > The patch is intended to add support for the QtMobility 1.2 package to OE.
>
> So apart from adding Qt Mobility this attempts to work around two issues by
> removing the checks rather than fixing the underlying cause of the checks
> failing. These checks look fine to me, so why are they not working?
>
These checks was not working because the file .../mkspecs/qconfig.pri
was not included to the main QtMobility project file. I include it
manually. Also I removed all .patch files because they deal with the
configuration, not with the code. You can find new version of the patch
here:
http://thread.gmane.org/gmane.comp.handhelds.openembedded.core/8708
Thanks,
Dima
^ permalink raw reply
* Re: [PATCH 1/1] cmake : Disable building ccmake.
From: Koen Kooi @ 2011-10-14 15:24 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <1318602698-13435-1-git-send-email-philip@balister.org>
Op 14 okt. 2011, om 16:31 heeft Philip Balister het volgende geschreven:
> ccmake fails to build due to an as-needed type error with -ltinfo. Disable
> it for now since the build fails and cmake is what we need for target
> sdk.
>
> Signed-off-by: Philip Balister <philip@balister.org>
> ---
> meta/recipes-devtools/cmake/cmake_2.8.5.bb | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/meta/recipes-devtools/cmake/cmake_2.8.5.bb b/meta/recipes-devtools/cmake/cmake_2.8.5.bb
> index 4fa9562..c0c5cad 100644
> --- a/meta/recipes-devtools/cmake/cmake_2.8.5.bb
> +++ b/meta/recipes-devtools/cmake/cmake_2.8.5.bb
> @@ -30,6 +30,7 @@ EXTRA_OECMAKE=" \
> -DCMAKE_DOC_DIR=${docdir_stripped}/cmake-${CMAKE_MAJOR_VERSION} \
> -DCMAKE_USE_SYSTEM_LIBRARIES=1 \
> -DKWSYS_CHAR_IS_SIGNED=1 \
> + -DBUILD_CursesDialog=0 \
> ${@base_contains('DISTRO_FEATURES', 'largefile', '-DKWSYS_LFS_WORKS=1', '-DKWSYS_LFS_DISABLE=1', d)} \
> "
Missing PR bump :)
^ permalink raw reply
* Re: [PATCH] qt4: Added support for QtMobility 1.2
From: Dmitry Cherukhin @ 2011-10-14 15:18 UTC (permalink / raw)
To: Saul Wold; +Cc: Patches and discussions about the oe-core layer
In-Reply-To: <4E810B74.7010001@linux.intel.com>
On Mon, 2011-09-26 at 16:32 -0700, Saul Wold wrote:
> On 09/23/2011 07:13 AM, Dmitry Cherukhin wrote:
> > This patch is indented to add new functionality,
> > specifically, the patch adds support for
> > the QtMobility 1.2 package.
> >
> > Added two recipes:
> > 1) qt-mobility-x11 builds the QtMobility 1.2 package
> > on the basis of qt4-x11-free;
> > 2) qt-mobility-embedded builds the QtMobility 1.2 package
> > on the basis of qt4-embedded.
> >
> > Signed-off-by: Dmitry Cherukhin<dima_ch@emcraft.com>
> > ---
> > meta/recipes-qt/qt4/files/qtm_qtmobility_pro.patch | 28 +++++++++++
> > meta/recipes-qt/qt4/files/qtme_gstreamer_pro.patch | 16 ++++++
> > meta/recipes-qt/qt4/qt-mobility-embedded_1.2.0.bb | 13 +++++
> > meta/recipes-qt/qt4/qt-mobility-x11_1.2.0.bb | 11 ++++
> > meta/recipes-qt/qt4/qt-mobility_1.2.0.inc | 51 ++++++++++++++++++++
> > 5 files changed, 119 insertions(+), 0 deletions(-)
> > create mode 100644 meta/recipes-qt/qt4/files/qtm_qtmobility_pro.patch
> > create mode 100644 meta/recipes-qt/qt4/files/qtme_gstreamer_pro.patch
> > create mode 100644 meta/recipes-qt/qt4/qt-mobility-embedded_1.2.0.bb
> > create mode 100644 meta/recipes-qt/qt4/qt-mobility-x11_1.2.0.bb
> > create mode 100644 meta/recipes-qt/qt4/qt-mobility_1.2.0.inc
> >
> > diff --git a/meta/recipes-qt/qt4/files/qtm_qtmobility_pro.patch b/meta/recipes-qt/qt4/files/qtm_qtmobility_pro.patch
> > new file mode 100644
> > index 0000000..689c224
> > --- /dev/null
> > +++ b/meta/recipes-qt/qt4/files/qtm_qtmobility_pro.patch
> > @@ -0,0 +1,28 @@
> > +This patch fixes the following issue at the configure stage:
> > + Project ERROR: Qt Mobility requires Qt 4.6 or higher. Qt was found.
> > +The version of Qt is already 4.7.3, so this is misconfiguration problem.
> > +
> > +The origin of this patch is:
> > + http://neophysis.git.sourceforge.net/git/gitweb.cgi?p=neophysis/openembedded;
> > + a=blob;f=recipes/neophysis/qt-mobility-1.0.0/qtmobility_pro.patch;
> > + h=fc5e1691aed47bc50d87e5c33497354182cacda4;hb=refs/heads/neophysis-testing-0.3
> > +Upstream-Status: not-appropriate
>
> Please refer to wiki page on www.openembedded.org for the corrcet
> formating of the Upstream-Status field. You are also missing a
> Signed-off-by: line for each patch file.
>
> (I would give the exact page, but the site appears to be having problems)
>
Thanks!
I removed all .patch files, new version of the patch is here:
http://thread.gmane.org/gmane.comp.handhelds.openembedded.core/8708
Dima
^ permalink raw reply
* Re: [PATCH] mesa-dri: Enable swrast only by default and intel drivers only on IA platform
From: Otavio Salvador @ 2011-10-14 14:46 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <1318603356.2342.20.camel@ted>
+1
Just another thing, I'd prefer to have DRIDRIVERS as ?= so machine can
override it.
On Fri, Oct 14, 2011 at 11:42, Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> ---
> diff --git a/meta/recipes-graphics/mesa/mesa-dri.inc b/meta/recipes-graphics/mesa/mesa-dri.inc
> index 603438e..795144a 100644
> --- a/meta/recipes-graphics/mesa/mesa-dri.inc
> +++ b/meta/recipes-graphics/mesa/mesa-dri.inc
> @@ -4,7 +4,11 @@ LIB_DEPS += "libdrm expat"
> # most of our targets do not have DRI so will use mesa-xlib
> DEFAULT_PREFERENCE = "-1"
>
> -EXTRA_OECONF += "--with-driver=dri --disable-egl --disable-gallium --without-gallium-drivers"
> +DRIDRIVERS = "swrast"
> +DRIDRIVERS_x86 = "swrast,i915,i965"
> +DRIDRIVERS_x86-64 = "swrast,i915,i965"
> +
> +EXTRA_OECONF += "--with-driver=dri --disable-egl --disable-gallium --without-gallium-drivers --with-dri-drivers=${DRIDRIVERS}"
>
> python populate_packages_prepend() {
> import os.path
> diff --git a/meta/recipes-graphics/mesa/mesa-dri_7.11.bb b/meta/recipes-graphics/mesa/mesa-dri_7.11.bb
> index 6a4f9a9..5d25127 100644
> --- a/meta/recipes-graphics/mesa/mesa-dri_7.11.bb
> +++ b/meta/recipes-graphics/mesa/mesa-dri_7.11.bb
> @@ -2,7 +2,3 @@ include mesa-common.inc
> include mesa-${PV}.inc
> include mesa-dri.inc
> PR = "${INC_PR}.0"
> -
> -EXTRA_OECONF += "--with-dri-drivers=swrast,i915,i965"
> -
> -COMPATIBLE_HOST = '(i.86.*-linux|x86_64.*-linux)'
> diff --git a/meta/recipes-graphics/mesa/mesa-dri_git.bb b/meta/recipes-graphics/mesa/mesa-dri_git.bb
> index 15cde60..a0e1945 100644
> --- a/meta/recipes-graphics/mesa/mesa-dri_git.bb
> +++ b/meta/recipes-graphics/mesa/mesa-dri_git.bb
> @@ -7,5 +7,3 @@ DEFAULT_PREFERENCE = "-2"
>
> PR = "${INC_PR}.0"
>
> -COMPATIBLE_HOST = '(i.86|x86_64).*-linux'
> -
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
--
Otavio Salvador O.S. Systems
E-mail: otavio@ossystems.com.br http://www.ossystems.com.br
Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br
^ permalink raw reply
* [PATCH] mesa-dri: Enable swrast only by default and intel drivers only on IA platform
From: Richard Purdie @ 2011-10-14 14:42 UTC (permalink / raw)
To: openembedded-core
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
diff --git a/meta/recipes-graphics/mesa/mesa-dri.inc b/meta/recipes-graphics/mesa/mesa-dri.inc
index 603438e..795144a 100644
--- a/meta/recipes-graphics/mesa/mesa-dri.inc
+++ b/meta/recipes-graphics/mesa/mesa-dri.inc
@@ -4,7 +4,11 @@ LIB_DEPS += "libdrm expat"
# most of our targets do not have DRI so will use mesa-xlib
DEFAULT_PREFERENCE = "-1"
-EXTRA_OECONF += "--with-driver=dri --disable-egl --disable-gallium --without-gallium-drivers"
+DRIDRIVERS = "swrast"
+DRIDRIVERS_x86 = "swrast,i915,i965"
+DRIDRIVERS_x86-64 = "swrast,i915,i965"
+
+EXTRA_OECONF += "--with-driver=dri --disable-egl --disable-gallium --without-gallium-drivers --with-dri-drivers=${DRIDRIVERS}"
python populate_packages_prepend() {
import os.path
diff --git a/meta/recipes-graphics/mesa/mesa-dri_7.11.bb b/meta/recipes-graphics/mesa/mesa-dri_7.11.bb
index 6a4f9a9..5d25127 100644
--- a/meta/recipes-graphics/mesa/mesa-dri_7.11.bb
+++ b/meta/recipes-graphics/mesa/mesa-dri_7.11.bb
@@ -2,7 +2,3 @@ include mesa-common.inc
include mesa-${PV}.inc
include mesa-dri.inc
PR = "${INC_PR}.0"
-
-EXTRA_OECONF += "--with-dri-drivers=swrast,i915,i965"
-
-COMPATIBLE_HOST = '(i.86.*-linux|x86_64.*-linux)'
diff --git a/meta/recipes-graphics/mesa/mesa-dri_git.bb b/meta/recipes-graphics/mesa/mesa-dri_git.bb
index 15cde60..a0e1945 100644
--- a/meta/recipes-graphics/mesa/mesa-dri_git.bb
+++ b/meta/recipes-graphics/mesa/mesa-dri_git.bb
@@ -7,5 +7,3 @@ DEFAULT_PREFERENCE = "-2"
PR = "${INC_PR}.0"
-COMPATIBLE_HOST = '(i.86|x86_64).*-linux'
-
^ permalink raw reply related
* [PATCH] arch-ia32: Add a generic x86 override (instead of i{3|4|5|6}86 and so on)
From: Richard Purdie @ 2011-10-14 14:41 UTC (permalink / raw)
To: openembedded-core
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
diff --git a/meta/conf/machine/include/ia32/arch-ia32.inc b/meta/conf/machine/include/ia32/arch-ia32.inc
index 96980d2..a52e33a 100644
--- a/meta/conf/machine/include/ia32/arch-ia32.inc
+++ b/meta/conf/machine/include/ia32/arch-ia32.inc
@@ -12,6 +12,7 @@ TUNEVALID[m32] = "IA32 ELF32 standard ABI"
TUNECONFLICTS[m32] = "m64 mx32"
TUNE_ARCH .= "${@bb.utils.contains("TUNE_FEATURES", "m32", "${X86ARCH32}", "" ,d)}"
TUNE_CCARGS += "${@bb.utils.contains("TUNE_FEATURES", "m32", "-m32", "", d)}"
+MACHINEOVERRIDES .= "${@bb.utils.contains("TUNE_FEATURES", "m32", ":x86", "" ,d)}"
# x32 ABI
TUNEVALID[mx32] = "IA32e (x86_64) ELF32 standard ABI"
^ permalink raw reply related
* [PATCH] bitbake.conf: Use TRANSLATED_TARGET_ARCH in OVERRIDES since any variable with _ in it isuseless there (e.g. x86_64)
From: Richard Purdie @ 2011-10-14 14:40 UTC (permalink / raw)
To: openembedded-core
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index a1420cf..0ae8059 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -666,7 +666,7 @@ AUTO_LIBNAME_PKGS = "${PACKAGES}"
#
# This works for functions as well, they are really just environment variables.
# Default OVERRIDES to make compilation fail fast in case of build system misconfiguration.
-OVERRIDES = "${TARGET_OS}:${TARGET_ARCH}:build-${BUILD_OS}:pn-${PN}:${MACHINEOVERRIDES}:${DISTROOVERRIDES}:forcevariable"
+OVERRIDES = "${TARGET_OS}:${TRANSLATED_TARGET_ARCH}:build-${BUILD_OS}:pn-${PN}:${MACHINEOVERRIDES}:${DISTROOVERRIDES}:forcevariable"
DISTROOVERRIDES ?= "${DISTRO}"
MACHINEOVERRIDES ?= "${MACHINE}"
^ permalink raw reply related
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox