On 5 Dec 2023, at 12:34, alper ak <[email protected]> wrote:
> The reason I deleted it is because there is a line in CMakeLists.txt
> like "set(CMAKE_INSTALL_RPATH "${CMAKE_INSTALL_PREFIX}/lib")" and that
> sets the runpath. If "foo.so" is not present in the runpath, as far as
> I know, every shared library is searched in the following locations:
> rpath -> LD_LIBRARY_PATH -> runpath -> ld.so.conf -> /lib and /usr/lib
> by default. I don't think there's any point in deleting the runpath.
Typically we don’t like rpaths in binaries at all, unless there’s a good
reason. There is logic in there to only set the RPATHs if the target isn’t a
“system” directory, but if the sanity checker didn’t start throwing warnings
then maybe the need for the RPATH removal has gone.
> I thought the user should know every option.
No: some packages have a _lot_ of options and we may want them always on or
always off, or have ways to control them implicitly without an explicit
PACKAGECONFIG.
> "Docs should be guarded
> on the api-documentation DISTRO_FEATURE", I don't understand exactly
> what this means.
Like this (made up example):
PACKAGECONFIG ??= "${@bb.utils.contains('DISTRO_FEATURES', 'api-documentation',
‘docs', '', d)}”
PACKAGECONFIG[docs] = “-Ddocs=true,-Ddocs=false,doxygen-native”
Cheers,
Ross
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#107223):
https://lists.openembedded.org/g/openembedded-devel/message/107223
Mute This Topic: https://lists.openembedded.org/mt/102978026/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
