I am peeking into a shared library using the nm tool. I have two versions of this library, and on each version, I have a definition for an overloaded typecast, namely Version 1 [email protected]:~frameworkPath1/lib $ nm -D libcomm.so | c++filt | grep comm::InstanceID::operator 000cda80 T comm::InstanceID::operator std::__cxx11::basic_string<char, std::char_traits, std::allocator () const Version 2 [email protected]:~frameworkPath2/lib $ ..
Category : abi
it seems I am having a linking problem. In my project im using a class that is defined in a header file, whose methods´ definitions lie in a precompiled library. I am using CMake and the compiling command includes the path to the precompiled library set correctly by the -L compiler flag. The linking problem ..
I want to pack an external library into my static library binary. But I’m afraid of user also has a different version of this external library. I want to remove non-API symbols from the final produced lib to prevent user linking to unwanted symbols from my lib. Is there any way to achieve it with ..
Say I have a static libA and a static libB. libA depends on libB, and libA and libB are linked together into an executable. Now I am working on a new program that also needs libA and libB. The only difference is some implementation of functions (and/or interface which are not called by libA) in ..
Motivation: Some libraries, e.g. Eigen have ABI that depends on compiler switches. Question: could users of this library somehow encode this behavior so that if you try to link components compiled with different compiler switches you get a linker error. So if it is not clear why I am asking about: Alice the library developer ..
Im currently trying to understand how Windows on ARM works. Im having trouble understanding how the ARM64EC ABI can work on an ARM chip. Microsoft says the ARM64EC is based on AArch64 with some changes to make it compatible to x64 including calling conventions, stack usage and data alignment [1]. In my mind this would ..
I’m trying to check if C++ still have issues with a stable ABI. I need a stable way to export / import an example API like this: class MY_API SomeBase { public: // … virtual std::vector<std::string> foo(const std::string& param) = 0; }; class MY_API SomeImpl : public SomeBase { public: std::vector<std::string> foo(const std::string& param) override ..
I do not understand how this can happen. In g++ I am getting an error that there is an ABI conflict between two routines defined in the same file, at the same time, under the same ABI directives. For reasons unknown the linker is searching for the C++11 version of a function, in spite of ..
Is there a way to check if GCC 10 and GCC 11 are compatible ? Say I have a library built with GCC 10 and I use this lib to build my project with GCC 11. Is it safe? Source: Windows Que..
I have a code that uses std=c++20. I want to use a C library that was build with old gcc version. Should I recompile the C library using the same compiler ? If no, how could you judge that the 2 ABIs are compatible? Source: Windows Que..
Web Development Company
Recent Comments