[Buildroot] Install to /lib usr /usr/lib ?

[Buildroot] Install to /lib usr /usr/lib ?

[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.

[Buildroot] Install to /lib usr /usr/lib ?

[Ulf Samuelsson]

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.

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

Best Regards
Ulf Samuelsson

[Buildroot] Install to /lib usr /usr/lib ?

[Bernhard Fischer]

On Thu, Jul 12, 2007 at 05:48:30PM +0200, Julien Letessier wrote:
>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)

No, this is not correct.
Everything that goes to $(STAGING_DIR)/include is wrong, it should be in
$(STAGING_DIR)/usr/include

Most of the packages should install into $(STAGING_DIR)/usr, a few
exceptions are allowed to go to $(STAGING_DIR)/lib (uClibc et al, refer
to your host for examples).

>* under $(STAGING_DIR)/usr/{bin,lib,include} and
>$(STAGING_DIR)/usr/{bin,lib} for other packages (e.g. gtk)
>
>Is this correct?

The scheme that is supposed to be used is to match a usual host as close
as possible. Some packages put their *.a into /usr/lib while they put
their *.so into /lib. Following this for the staging_dir is ok iff your
host hints it.
>
>If so, we have a problem.
>Half the of the package/*/*.mk use one option, half use the other.

The consistency is relatively new, alot of packages still do install
into $(STAGING_DIR) directly and have to be fixed to install into
$(STAGING_DIR)/usr. I corrected some already, patches to fix the rest
are very welcome.

>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

[Buildroot] Install to /lib usr /usr/lib ?

[Bernhard Fischer]

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,