https://bugs.kde.org/show_bug.cgi?id=401742
Mark Wielaard <m...@klomp.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |m...@klomp.org
--- Comment #11 from Mark Wielaard <m...@klomp.org> ---
To add to what Tom and Philippe said above the .a files are static archives
that are installed to make it possible to create your own valgrind tools. When
creating such tools they will need to be statically linked (valgrind tools
cannot depend on shared libraries). Since they are statically linked they seem
ideal candidates for LTO. But it sounds like this isn't really an anticipated
use case for LTO?
Note that this isn't really something most people do. In Fedora the archives
and the header files to build your own valgrind tools are put in a separate
package (valgrind-tools-devel) and I don't really know if anybody every uses
this subpackage (no other package in the distro depends on it). There is a
"normal" valgrind-devel package too, which contains the header files that
valgrind aware programs/libraries depend on. And that one is actually used by
various other packages.
--
You are receiving this mail because:
You are watching all bug changes.
