Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] bzip2: introduce make variable LIBDIR
Date: Fri, 24 Nov 2017 23:35:07 +0100	[thread overview]
Message-ID: <20171124233507.4f398629@windsurf.lan> (raw)
In-Reply-To: <20171124220554.24261-1-code@mmayer.net>

Hello,

On Fri, 24 Nov 2017 14:05:54 -0800, Markus Mayer wrote:
> From: Markus Mayer <mmayer@broadcom.com>
> 
> In order to allow us to install libz2 into a location other than
> /usr/lib, we introduce a variable called LIBDIR that can be set by
> the build system to an alternate location.
> 
> LIBDIR defaults to /usr/lib, so the behaviour doesn't change if
> LIBDIR is never set.
> 
> Signed-off-by: Markus Mayer <mmayer@broadcom.com>
> ---
> 
> Most package in buildroot seem to offer the flexibility to install
> libraries into directories specified by the user (build system) rather
> than hard-coding the destination in the way bzip2 does.

We don't support customizing on a per-package basis, or even globally,
where libraries are installed. Where have you seen that we offer the
flexibility to choose where libraries are installed ?

> My question is whether patches 2-4 should be combined into a single
> patch or if it is preferable to keep them separate.

The whole point of patch 2 is to allow cross-compilation, not to allow
customizing the directory where libraries are installed.

What are you trying to do?

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-11-24 22:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-24 22:05 [Buildroot] [RFC] bzip2: introduce make variable LIBDIR Markus Mayer
2017-11-24 22:35 ` Thomas Petazzoni [this message]
2017-11-25  0:24   ` Markus Mayer

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=20171124233507.4f398629@windsurf.lan \
    --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