[Angstrom-devel] [meta-oe][PATCH v2] qwt-e: qwt 6.1.0 FTBFS fix for qt-embedded targets

2014-04-14 Thread Björn Krombholz 
QWT 6.1.0 changed the handling of the QT_INFIX variable.
Builds with any QT_INFIX defined will fail as the generated qmake TARGET
is always libqwt.* ignoring the INFIX. Sub-projects like designer respect
the INFIX variable however and won't find the libqwtE*.so.

Signed-off-by: Björn Krombholz b.krombh...@pironex.de
---
For angstrom-staging-yocto1.4 branch, no QWT 6.1.0 in 1.5+ yet.

Accidentally posted to oe-devel list, while it's only relevant to
the Angstrom repo of meta-openembedded

v2: removed PR/INC_PR, moved the SRC_URI modification to the .bb file 
as it is only useful for qwt-e and the particular version 6.1.0.

 meta-oe/recipes-qt/qwt/files/qwt-e_qt_infix.patch | 13 +
 meta-oe/recipes-qt/qwt/qwt-e_6.1.0.bb |  3 +++
 2 files changed, 16 insertions(+)
 create mode 100644 meta-oe/recipes-qt/qwt/files/qwt-e_qt_infix.patch

diff --git a/meta-oe/recipes-qt/qwt/files/qwt-e_qt_infix.patch 
b/meta-oe/recipes-qt/qwt/files/qwt-e_qt_infix.patch
new file mode 100644
index 000..3a6fb64
--- /dev/null
+++ b/meta-oe/recipes-qt/qwt/files/qwt-e_qt_infix.patch
@@ -0,0 +1,13 @@
+Index: qwt-6.1.0/qwtfunctions.pri
+===
+--- qwt-6.1.0.orig/qwtfunctions.pri2014-04-11 16:25:59.291152505 +0200
 qwt-6.1.0/qwtfunctions.pri 2014-04-11 16:26:25.749892402 +0200
+@@ -12,7 +12,7 @@
+ defineReplace(qwtLibraryTarget) {
+ 
+ unset(LIBRARY_NAME)
+-LIBRARY_NAME = $$1
++LIBRARY_NAME = $$1$${QT_LIBINFIX}
+ 
+ mac:contains(QWT_CONFIG, QwtFramework) {
+ 
diff --git a/meta-oe/recipes-qt/qwt/qwt-e_6.1.0.bb 
b/meta-oe/recipes-qt/qwt/qwt-e_6.1.0.bb
index 7694514..4d23bc0 100644
--- a/meta-oe/recipes-qt/qwt/qwt-e_6.1.0.bb
+++ b/meta-oe/recipes-qt/qwt/qwt-e_6.1.0.bb
@@ -2,6 +2,9 @@ inherit qt4e
 
 require qwt.inc
 
+SRC_URI += file://qwt-e_qt_infix.patch \
+
+
 SRC_URI[qwt.md5sum] = aef0437b37f191067a6a9dc01c30ba64
 SRC_URI[qwt.sha256sum] = 
a7e3d9f1db917d186a973c5f04a316bc9607c7c35794d7a16de323aba5e17402
 
-- 
1.9.2


___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] v2013.06 and v2013.12 architecture change for ARMv7A machines

2013-10-23 Thread Björn Krombholz 

On 10/20/2013 09:04 PM, Koen Kooi wrote:

Then I noticed that the 'genericarmv7a' machine in meta-linaro set
the DEFAULTTUNE to armv7athf-neon. A MACHINE config shouldn't set
that variable, but that's a different bug. It turns out that using
that tune we can have a single feed again for all armv7a machines.


Hi,

just for clarification, I'm not sure where to set it if not in the 
MACHINE config without modifying meta-angstrom.


I've seen you added MACHINE specific DEFAULTTUNEs based on the currently 
supported boards.

Basically the result should be (IMHO):
if MACHINE is a armv7a based and DISTRO is angstrom, then
DEFAULTTUNE = armv7athf-neon

Would it be possible to add those definitions based on SOC_FAMILY:
DEFAULTTUNE_ti33x and DEFAULTTUNE_omap3?

As of now, when I add a new MACHINE=machfoo based on ti33x.inc from 
meta-ti, I end up with a DEFAULTTUNE=armv7a-neon instead of the new one, 
as the board is not known in meta-angstrom.


I added
DEFAULTTUNE_machfoo = ${DEFAULTTUNE_genericarmv7a}
to the machfoo.conf which is discouraged, if I understand you correctly.

Maybe I'm just missing the obvious safe way?

Thx
Björn

--
Björn Krombholz
pironex GmbH -- http://www.pironex.de

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

[Angstrom-devel] Craneboard and more recent kernel / WL1271 via SDIO

2011-07-27 Thread Björn Krombholz 

Hi,

I'm currently trying to connect a WL1271 based expansion to a Craneboard.

My problem is, that the current development on Craneboard looks pretty 
dead, but the WL1271 with SDIO is only available in Kernel 2.6.37+.


Does someone know, if there is still someone trying to update the in 
kernel craneboard support? There is a basic board file in 2.6.37, but 
that's far from being bootable.


Does someone know an alternative git repository I might have missed 
while searching?


Or does someone know of a working backport of the neccessary SDIO code 
to 2.6.32?


I'd be grateful for any hint in one way or another.

Thx
Björn



___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel