From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] live555: fix library installation
Date: Mon, 20 Apr 2015 10:56:13 +0200 [thread overview]
Message-ID: <20150420105613.7c8262d3@free-electrons.com> (raw)
In-Reply-To: <5534BAF3.1080305@lucaceresoli.net>
Dear Luca Ceresoli,
On Mon, 20 Apr 2015 10:38:11 +0200, Luca Ceresoli wrote:
> At first I just wanted to keep a sort of "backward compatibility", at
> least at the configure level. But I really prefer to simplify the
> package by installing everything.
Well, it's not really "backward compatible" because now you have 3
options to enable/disable the installation of 3 binaries, but the
package nonetheless installs gazillions of other binaries. So it
doesn't make much sense to have options just for those 3 binaries.
> BTW, there should be a simple way to skip installation of all
> executables, by tweaking the live555 makefiles. But I don't think it
> would be very nice to conditionally apply a patch based on config
> options. Do you agree?
No, conditional patches are a no-go. This would only be possible if you
had a patch that can always be applied, and then the .mk file calls
"make install-all" or "make install-lib" or something like that. But if
it's not planned in the live555 build system, I don't think it's really
worth doing the change.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-04-20 8:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 14:50 [Buildroot] [PATCH] live555: fix library installation Luca Ceresoli
2015-04-19 11:42 ` Thomas Petazzoni
2015-04-20 8:38 ` Luca Ceresoli
2015-04-20 8:56 ` Thomas Petazzoni [this message]
2015-04-20 9:00 ` Luca Ceresoli
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=20150420105613.7c8262d3@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox