On Mittwoch, 10. August 2022 11:56:46 CEST Jan Engelhardt wrote:
On Wednesday 2022-08-10 11:47, Konstantin Voinov wrote:
Yes, but it doesn't work, for some of my packages at least. CMAKE_SKIP_BUILD_RPATH - does
cmake's questionable naming scheme :-/
More pointless bashing ... BUILD_RPATH is set/used before installing. It is required so unit tests can be run in the build tree.
cmake and its questionable defaults :-/
-DCMAKE_SKIP_RPATH:BOOL=ON -DCMAKE_SKIP_INSTALL_RPATH:BOOL=ON
Speaking of it, can't we just slap all of this into %cmake?
It is there, but it is an inconsistent mess, being different in TW, Leap 15.3 and 15.4.
I can't see the legitimacy of rpaths in FHS-conforming packages (and for instances where it's needed, it could just be enabled on a case-by-case basis)
Citing from FHS 3.0:
Applications may use a single subdirectory under /usr/lib. If an application uses a subdirectory, all architecture-dependent data exclusively used by the application must be placed within that subdirectory.
So using RUNPATHs for the subdirectories is legitimate and required. Regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen phone: +49 241 53809034 mobile: +49 151 50412019