Language Selection

English French German Italian Portuguese Spanish

One more reason not to trust CMake

Filed under
Software

So everybody says that CMake is great because it’s faster. Of course CMake achieves speed with an approach different from the one autotools have, that is, they don’t discover features, they apply knowledge. Hey it’s a valid method as any other, if you actually know what you are doing, and if you can keep up with variants and all the rest. Another thing that it does is to avoid the re-linking during the install phase.

Let me try to explain why re-linking exists: when you build a project using libtool, there might be binaries (executables and/or libraries) that depend on shared libraries that are being built in the same source tree. When you run the executables from the source tree, you want them to be used. When you install, as you might be installing just a subtree of the original software, libtool tries to guess if you just installed the library or not (often making mistakes) and if not, it re-links the target, that is, recreates it from scratch to link to the system library. In the case of packages built by ebuild, by the use of DESTDIR, we almost always have the relinking stage in there. Given that GNU ld is slow (and IMHO should be improved, rather than replaced by gold, but that’s material for another post), it’s a very wasteful process indeed, and libtool should be fixed not to perform that stage every time.

One of the things that the relinking stage is supposed to take care is to replace the rpath entries. An rpath entry specify to the runtime linker (ld.so) where to find the dependent libraries outside of the usual library paths (that is /etc/ld.so.conf and LD_LIBRARY_PATH). It’s used for non-standard install directories (for instance for internal libraries that should never be linked against) or during the in-tree execution of software, so that the just-built libraries are preferred over the ones in the system already.

So to make the install phase faster in CMake, they decided, with 2.6 series, to avoid the relinking, by messing with the rpath entries directly. It would be all fine and nice if they did it correctly of course.

MOre Here




More in Tux Machines

Linux and Linux Foundation

Security Leftovers

Qt 5.10 and digiKam

  • Qt 5.10 Platform Support Changes Being Discussed
    Qt developers have begun a fresh round of discussions over the supported platforms / operating systems of Qt 5.10 that will be released in the later part of this calendar years. Among the officially supported Linux distribution changes would be moving to RHEL 7.3, openSUSE Leap 42.2, Ubuntu 17.04 (still keeping around 16.04 LTS too), moving the Windows MinGW to MinGW 6.3, and more.
  • digiKam – A Professional Photo Editing and Management Software
    digiKam is an advanced cross-platform digital photo management app inspired by photographers’ needs to view, tweak, enhance, organize, and share photographs across Linux systems. It possesses all the tools and feature set necessary to process, manage, organize, and transfer photographs, videos, and RAW files – while consistently receiving optimization upgrades to its feature set and workflow.

GNOME/Unity in Ubuntu