From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Bizarre things on the allyespackageconfig build
Date: Fri, 10 May 2013 23:52:58 +0200 [thread overview]
Message-ID: <518D6C3A.1090400@mind.be> (raw)
In-Reply-To: <20130510175133.13d3fc6f@skate>
On 10/05/13 17:51, Thomas Petazzoni wrote:
> * qt installs its demos and examples in usr/share/qt/{demos,examples},
> but it installs both the source code and binaries. It would probably
> make sense to get rid of the source code of the examples.
Since the demos/examples are typically not installed in a production
system but just during development or to showcase things, I don't think
it is worth the effort to hack the makefiles or to do explicit
post-processing to remove the source code. If the user wants it, it can
still be done in a post-build script.
Same goes for qt5, edje, etc.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
prev parent reply other threads:[~2013-05-10 21:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 15:51 [Buildroot] Bizarre things on the allyespackageconfig build Thomas Petazzoni
2013-05-10 16:53 ` Yann E. MORIN
2013-05-10 20:58 ` Thomas Petazzoni
2013-05-10 22:27 ` Yann E. MORIN
2013-05-11 10:31 ` Thomas Petazzoni
2013-05-12 17:29 ` Yann E. MORIN
2013-05-12 19:38 ` Peter Korsgaard
2013-05-10 21:52 ` Arnout Vandecappelle [this message]
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=518D6C3A.1090400@mind.be \
--to=arnout@mind.be \
--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.