From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] qtuio: new package
Date: Thu, 25 Oct 2012 08:56:32 +0200 [thread overview]
Message-ID: <20121025085632.30c9878f@skate> (raw)
In-Reply-To: <1348297189-29498-1-git-send-email-sho@relinux.de>
Dear Stephan Hoffmann,
On Sat, 22 Sep 2012 08:59:49 +0200, Stephan Hoffmann wrote:
> Implementation of an interface connecting TUIO messages and QT events
>
> https://github.com/x29a/qTUIO
>
> Signed-off-by: Stephan Hoffmann <sho@relinux.de>
> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> Tested-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> build-tested with a minimal internal toolchain for ARM.
> ---
> package/Config.in | 6 ++++
> package/qtuio/Config.in | 18 ++++++++++++
> package/qtuio/qtuio.mk | 70 +++++++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 94 insertions(+), 0 deletions(-)
> create mode 100644 package/qtuio/Config.in
> create mode 100644 package/qtuio/qtuio.mk
Looks like it breaks the build in certain configurations:
http://autobuild.buildroot.net/results/c4a12fe6b8e7eb8c31ee2fd48893480bd098a008/build-end.log
It seems like a debug version of the library, named libqTUIO_d.so, has
been generated, which prevents the install rules from working.
Could you have a look into this? Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-10-25 6:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-22 6:59 [Buildroot] [PATCH] qtuio: new package Stephan Hoffmann
2012-10-21 19:47 ` Peter Korsgaard
2012-10-25 6:56 ` Thomas Petazzoni [this message]
2012-10-25 7:09 ` Samuel Martin
2012-10-25 7:28 ` Stephan Hoffmann
-- strict thread matches above, loose matches on Subject: below --
2012-08-30 12:08 Stephan Hoffmann
2012-09-11 21:38 ` Arnout Vandecappelle
2012-09-12 7:13 ` Arnout Vandecappelle
2012-08-30 9:59 Stephan Hoffmann
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=20121025085632.30c9878f@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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.