]> code.ossystems Code Review - openembedded-core.git/commit
bitbake: set default libexecdir to $prefix/libexec
authorRoss Burton <ross.burton@intel.com>
Tue, 30 Apr 2013 19:35:54 +0000 (20:35 +0100)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Fri, 22 Jan 2016 23:42:38 +0000 (23:42 +0000)
commite7270e331560546d3805cd66ed14afcbc96b6d89
tree9430f2f42e3f2babfc131a47b6979eb2316a4398
parent0dc0d23962312b4985eebaf32073d3f4a5d8081b
bitbake: set default libexecdir to $prefix/libexec

The use of $libdir/$BPN as libexecdir is contrary to all other mainstream
distributions (which either use $prefix/libexec or $libdir), and the GNU Coding
Standards[1] which suggests $prefix/libexec and notes that any package-specific
nesting should be done by the package itself.  Finally, having libexecdir change
between recipes makes it very difficult for different recipes to invoke binaries
that have been installed into libexecdir.  The File System Hierarchy[2] now
recognises the use of $prefix/libexec/, giving distributions the choice of
$prefix/lib or $prefix/libexec without breaking FHS.

Change bitbake.conf to use $prefix/libexec for libexecdir, so that the binaries
are separated from the libraries.  This should avoid complications with multilib
configurations.

[1] https://www.gnu.org/prep/standards/html_node/Directory-Variables.html
[2] http://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch04s07.html

[ YOCTO #6398 ]

Signed-off-by: Ross Burton <ross.burton@intel.com>
meta/conf/bitbake.conf