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][PATCH 0/5] qt-creator for target machine
Date: Wed, 28 Jan 2015 11:51:48 +0100	[thread overview]
Message-ID: <20150128105148.GE2477@jama> (raw)
In-Reply-To: <1422338033-18521-1-git-send-email-schnitzeltony@googlemail.com>

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

On Tue, Jan 27, 2015 at 06:53:48AM +0100, Andreas Müller wrote:
> These patches were build tested for 5.4.0 with all qt5 recipes I am working on
> currently (kf5/hawaii/mauii). Git versions were not yet tested.
> On target:
> 
> * toolchain was set
> * QT5 c++ project was build and debugged
> 
> We shall see what Martin's world says - maybe we need a EXCLUDE_FROM_WORLD for
> meta-oe's qt-creator (conditional on meta-qt5 included in layer).

One of these is causing qtbase_git build failure:

| generators/win32/cesdkhandler.cpp:96: error: undefined reference to 'QDebug::~QDebug()'
| ../src/corelib/io/qdir.cpp:2330: error: undefined reference to 'QDebug::~QDebug()'
| ../src/corelib/io/qdir.cpp:2330: error: undefined reference to 'QDebug::~QDebug()'
| ../src/corelib/io/qdir.cpp:2328: error: undefined reference to 'QDebug::~QDebug()'
| collect2: error: ld returned 1 exit status
| make: *** [bin/qmake] Error 1
| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_compile (log file is located at /home/jenkins/oe/world/shr-core/tmp-glibc/work/armv5te-oe-linux-gnueabi/qtbase/5.4.0+gitAUTOINC+47326b9c5c-r0/temp/log.do_compile.23226)

> Andreas Müller (5):
>   qtbase: remove patches required for native(-sdk) only
>   qtbase/EXTERNAL_HOST_BINS: split out code only required for
>     native-(sdk)
>   qtbase: build qmake for target with paths aligned
>   qt5-creator: add 3.3.0 of qt-creator
>   add gdb append to enable python packageconfig
> 
>  recipes-devtools/gdb/gdb_%.bbappend                |   1 +
>  recipes-qt/qt5/nativesdk-qtbase.inc                |   1 +
>  recipes-qt/qt5/nativesdk-qtbase_git.bb             |   1 +
>  ...t-creator-to-build-on-arm-aarch32-and-aar.patch |  94 ++++++++++++++++++
>  recipes-qt/qt5/qt5-creator/qtcreator.desktop.in    |  10 ++
>  recipes-qt/qt5/qt5-creator_3.3.0.bb                |  87 +++++++++++++++++
>  recipes-qt/qt5/qtbase-native.inc                   |   1 +
>  recipes-qt/qt5/qtbase.inc                          |  27 +++---
>  .../0003-Add-external-hostbindir-option.patch      |  75 ---------------
>  ...-build-it-in-configure-but-allow-to-build.patch |  27 ++++--
>  ...014-Add-external-hostbindir-option-native.patch | 106 +++++++++++++++++++++
>  .../0015-Set-paths-for-target-properly.patch       |  72 ++++++++++++++
>  recipes-qt/qt5/qtbase_git.bb                       |   3 +-
>  13 files changed, 407 insertions(+), 98 deletions(-)
>  create mode 100644 recipes-devtools/gdb/gdb_%.bbappend
>  create mode 100644 recipes-qt/qt5/qt5-creator/0001-Fix-Allow-qt-creator-to-build-on-arm-aarch32-and-aar.patch
>  create mode 100644 recipes-qt/qt5/qt5-creator/qtcreator.desktop.in
>  create mode 100644 recipes-qt/qt5/qt5-creator_3.3.0.bb
>  create mode 100644 recipes-qt/qt5/qtbase/0014-Add-external-hostbindir-option-native.patch
>  create mode 100644 recipes-qt/qt5/qtbase/0015-Set-paths-for-target-properly.patch
> 
> -- 
> 1.8.3.1
> 
> -- 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel

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

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

  parent reply	other threads:[~2015-01-28 10:51 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-27  5:53 [meta-qt5][PATCH 0/5] qt-creator for target machine Andreas Müller
2015-01-27  5:53 ` [meta-qt5][PATCH 1/5] qtbase: remove patches required for native(-sdk) only Andreas Müller
2015-02-18 16:09   ` Martin Jansa
2015-02-18 17:35     ` Andreas Müller
2015-02-19 14:47       ` Martin Jansa
2015-02-19 15:30         ` Andreas Müller
2015-02-19 16:14           ` Martin Jansa
2015-01-27  5:53 ` [meta-qt5][PATCH 2/5] qtbase/EXTERNAL_HOST_BINS: split out code only required for native-(sdk) Andreas Müller
2015-01-27  5:53 ` [meta-qt5][PATCH 3/5] qtbase: build qmake for target with paths aligned Andreas Müller
2015-01-27  5:53 ` [meta-qt5][PATCH 4/5] qt5-creator: add 3.3.0 of qt-creator Andreas Müller
2015-02-05 15:18   ` Raphael Philipe
2015-02-05 16:11     ` Andreas Müller
2015-02-05 16:15       ` Andreas Müller
2015-02-05 17:22         ` Raphael Philipe
2015-02-05 17:27           ` Otavio Salvador
2015-02-05 20:34           ` Andreas Müller
2015-02-06  0:27             ` Firstname Lastname
2015-02-11 15:10               ` Raphael Philipe
2015-02-11 16:59                 ` Andreas Müller
2015-02-27  6:50   ` Martin Jansa
2015-02-27  8:33     ` Andreas Müller
2015-02-27  8:34     ` Martin Jansa
2015-02-27  8:36       ` Andreas Müller
2015-01-27  5:53 ` [meta-qt5][PATCH 5/5] add gdb append to enable python packageconfig Andreas Müller
2015-01-28 10:51 ` Martin Jansa [this message]
2015-01-28 12:13   ` [meta-qt5][PATCH 0/5] qt-creator for target machine Andreas Müller

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=20150128105148.GE2477@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.