diff options
author | Ross Burton <ross.burton@intel.com> | 2013-04-30 20:35:54 +0100 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2016-01-24 09:40:21 +0000 |
commit | f35b2e29d9bfa817e64b83df11ebbbfe0f4e8e5c (patch) | |
tree | 504af54a7f43135dc32fb97a4eaf7bf143995bf8 /meta/recipes-rt | |
parent | 40f0c2d7427ca62a8f268d61691039c5f73a1d4c (diff) | |
download | poky-f35b2e29d9bfa817e64b83df11ebbbfe0f4e8e5c.tar.gz |
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 ]
(From OE-Core rev: e7270e331560546d3805cd66ed14afcbc96b6d89)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-rt')
0 files changed, 0 insertions, 0 deletions