Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Install to /lib usr /usr/lib ?
Date: Fri, 13 Jul 2007 14:09:55 +0200	[thread overview]
Message-ID: <20070713120955.GB32559@aon.at> (raw)
In-Reply-To: <1184258335.5175.44.camel@elrond.sweden.atmel.com>

On Thu, Jul 12, 2007 at 06:38:55PM +0200, Ulf Samuelsson wrote:
>tor 2007-07-12 klockan 17:48 +0200 skrev Julien Letessier:
>> Dear buildroot maintainers,
>> 
>> For the relative newcomer I am, there seems to be a lot of
>> inconsistency in buildroot for package installation directories.
>> 
>> From what I undrestand, the policy is to install packages:
>> * under $(STAGING_DIR)/{bin,lib,include} and $(STAGING_DIR)/{bin,lib}
>> for the toolchain (e.g. uclibc)
>> * under $(STAGING_DIR)/usr/{bin,lib,include} and
>> $(STAGING_DIR)/usr/{bin,lib} for other packages (e.g. gtk)
>> 
>
>As I interpret things,
>Only host tools should be installed in $(STAGING_DIR)
>
>Target tools gets installed somewhere in $(TARGET_DIR) which
>now is defined to be project_build_ARCH/$(PROJECT)/root
>
>
>> Is this correct?
>> 
>> If so, we have a problem.
>> Half the of the package/*/*.mk use one option, half use the other.
>> As I "svn uped" today, the fontconfig package I had a hard time
>> patching broke, because expat decided AGAIN to install directly under
>> /lib.
>> 
>> Please, please establish a clear policy on this, so we can start
>> submiting patches
>
>I think that /usr/bin/X11 might be the right directory to
>use, at least for your X11R7 stuff.

wasn't the new LSB directive that even X11 binaries should go to
/usr/bin and *not* into /usr/bin/X11Rwhatever.proto_rev

>I would check where the package is located on my normal linux host
>and select the same install dir for the buildroot target.

Well yes, to some extent. Alot of distros violate LSB in various ways.
Since debian is (last time i looked) the distribution that violates LSB
least (only a very few violations, really), you can settle to follow
suit what debian does.

If you are unlucky and don't have a current debian-box then either do
yourself a favour and install it, or go to packages.debian.org/ and
select "search content of packages" to see where the stuff should be
installed to.

HTH,

  reply	other threads:[~2007-07-13 12:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-12 15:48 [Buildroot] Install to /lib usr /usr/lib ? Julien Letessier
2007-07-12 16:38 ` Ulf Samuelsson
2007-07-13 12:09   ` Bernhard Fischer [this message]
2007-07-13 12:04 ` Bernhard Fischer

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=20070713120955.GB32559@aon.at \
    --to=rep.dot.nop@gmail.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