How to make a header-only library with cmake? Like this: add_library(project INTERFACE) target_include_directories(project INTERFACE .) Then in the target that uses the library: target_link_libraries(dependee PUBLIC/INTERFACE/PRIVATE # pick one project) and include the header like this: #include <project/folder1/file.hpp>
Why is it that when you create a Windows DLL it requires the client program to also link against a static library (.lib file), but applications created in Linux does not require any linking against such static library. This is a historic design decision made by Microsoft so that the linker could add DLL references … Read more
In general, running binaries that were compiled for an older glibc version (e.g. 2.13) will run fine on a system with a newer glibc (e.g. 2.14, like your system). Running a binary that was built for a newer glibc (e.g. 2.15, like the one that fails) on a system with an older glibc will probably … Read more
You can use auditwheel to inject the external libraries into the wheel: auditwheel repair: copies these external shared libraries into the wheel itself, and automatically modifies the appropriate RPATH entries such that these libraries will be picked up at runtime. This accomplishes a similar result as if the libraries had been statically linked without requiring … Read more
Some Background Shared libraries in C++ are quite difficult because the standard says nothing about them. This means that every platform has a different way of doing them. If we restrict ourselves to Windows and some *nix variant (anything ELF), the differences are subtle. The first difference is Shared Object Visibility. It is highly recommended … Read more
The evils of too much coupling between services are far worse than the problems caused by code duplication The author is very unspecific when he uses the generic word “coupling”. I would agree with certain types of coupling being a strict no-no (like sharing databases or using internal interfaces). However the use of common libraries … Read more
You can specify the full path to the static libs without the -l flag to link with those. gcc … source.c … /usr/lib32/libmysuperlib.a …
According to the docs: This instructs the linker to add all symbols, not only used ones, to the dynamic symbol table. Those are not debug symbols, they are dynamic linker symbols. Those are not removed by strip since it would (in most cases) break the executable – they are used by the runtime linker to … Read more
I solved this issue with “Embedded Binaries” in the General project settings.
You can use the __attribute__((constructor)) and __attribute__((destructor)) to execute code on load and unload of the shared library.