From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Qt mouse, keyboard, touchscreen
Date: Wed, 28 Nov 2012 14:00:30 +0100 [thread overview]
Message-ID: <20121128140030.42c255c9@skate> (raw)
In-Reply-To: <1354102604.50307.YahooMailNeo@web164602.mail.gq1.yahoo.com>
Dear Zoran Djordjevic,
On Wed, 28 Nov 2012 03:36:44 -0800 (PST), Zoran Djordjevic wrote:
> I've tried patch, you submitted, and then make qt-reconfigure and
qt-reconfigure will not re-extract the source code and apply the
patches, so it is not appropriate. If you want to rebuild a package
from scratch, including extracting the package and applying the
patches, do:
make qt-dirclean
> receive strange error about include folders. Same error I had
> earlier when trying with deleting stamp files (when added some
> options regarding Qt in Buildroot's menuconfig), and in that case
> I had to do make clean all. But if I do so, now, I think I will loose my
> patched files (am I right ?)
If you made changes to output/build/<something>/, yes, you will loose
your changes. But you shouldn't be making any change in
output/build/<something>/
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-11-28 13:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-24 9:19 [Buildroot] Qt mouse, keyboard, touchscreen Zoran Djordjevic
2012-11-24 9:51 ` Stephan Hoffmann
2012-11-26 7:49 ` Zoran Djordjevic
2012-11-26 8:00 ` Stephan Hoffmann
[not found] ` <50B3210E.2010806@relinux.de>
[not found] ` <1353917395.39625.YahooMailNeo@web164603.mail.gq1.yahoo.com>
2012-11-26 8:17 ` Stephan Hoffmann
2012-11-27 7:46 ` Zoran Djordjevic
2012-11-27 15:27 ` Stephan Hoffmann
2012-11-27 15:30 ` Thomas Petazzoni
2012-11-28 11:36 ` Zoran Djordjevic
2012-11-28 13:00 ` Thomas Petazzoni [this message]
2012-11-28 17:11 ` Zoran Djordjevic
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=20121128140030.42c255c9@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.