static-linking

问题 I want to selectively link libm.a statically, all the other libraries ( libc.so included) dinamically. But if I use the math functions from math.h , it almost always fails to link correctly. Why? And why does it work sometimes? (For example if I only use sqrt , fabs or, strangely, tanh , it seems to link correctly) myscript.sh: #!/bin/bash for i in sqrt tanh sin tan do echo "-----$i----------" sed "s/ciao/$i/" prova.c >provat.c gcc provat.c -fno-builtin -l:libm.a [[ $? -eq 0 ]] && { echo -n "

问题 My executables are linked with many static libraries, typically between 50 and 100 archives on Linux. Occasionally there are dependency cycles in these archives. The order that these libraries appear on the link command line is significant, see here. Attempting to manually order this many libraries is time-consuming at minimum, especially when there are cycles present. Question: is there a utility or technique that will analyze a code base and produce a correct link command line ordering? 回答1

问题 I want to use g2o library in my C++11 project on Ubuntu 18.04, but I cannot make build working. I have all the dependencies. But I cannot link g2o library to my project via CMakeLists.txt I am a newbie in C++ dependencies. I've tried cloning https://github.com/RainerKuemmerle/g2o repository and building it with cmake. The structure is as following: MY_PROJECT |__ cmake_modules |__ project_src |__ CMakeLists.txt |__ Thirdparty |____ g2o |____ bin |____ build |____ cmake_modules # findG2O.cmake

问题 I want to use g2o library in my C++11 project on Ubuntu 18.04, but I cannot make build working. I have all the dependencies. But I cannot link g2o library to my project via CMakeLists.txt I am a newbie in C++ dependencies. I've tried cloning https://github.com/RainerKuemmerle/g2o repository and building it with cmake. The structure is as following: MY_PROJECT |__ cmake_modules |__ project_src |__ CMakeLists.txt |__ Thirdparty |____ g2o |____ bin |____ build |____ cmake_modules # findG2O.cmake

问题 What I want to do I try to separate my code into modules, which are compiled as static libraries with the -fPIC option. Finally, they are to be linked into a shared library using --whole-archive , also compiled with -fPIC . For the whole compilation, I use CMake generated make files and C++17 with GCC8 ! Problem Trying to do so with GCC8 x86_64 and libstdc++_pic fails with: /usr/bin/x86_64-linux-gnu-ld: CMakeFiles/shirabeengine.dir/code/source/core/engine.cpp.o: relocation R_X86_64_PC32

问题 What I want to do I try to separate my code into modules, which are compiled as static libraries with the -fPIC option. Finally, they are to be linked into a shared library using --whole-archive , also compiled with -fPIC . For the whole compilation, I use CMake generated make files and C++17 with GCC8 ! Problem Trying to do so with GCC8 x86_64 and libstdc++_pic fails with: /usr/bin/x86_64-linux-gnu-ld: CMakeFiles/shirabeengine.dir/code/source/core/engine.cpp.o: relocation R_X86_64_PC32

问题 What I want to do I try to separate my code into modules, which are compiled as static libraries with the -fPIC option. Finally, they are to be linked into a shared library using --whole-archive , also compiled with -fPIC . For the whole compilation, I use CMake generated make files and C++17 with GCC8 ! Problem Trying to do so with GCC8 x86_64 and libstdc++_pic fails with: /usr/bin/x86_64-linux-gnu-ld: CMakeFiles/shirabeengine.dir/code/source/core/engine.cpp.o: relocation R_X86_64_PC32

问题 I always have problems when building libraries and linking them, so I hope someone can give me a hand. I downloaded libtorrent from here and I've built it like they explain here in the building with autotools section (skipping step 1). The building process was successfull I think, but when I did make check the output was: ============================================================================ Testsuite summary for libtorrent-rasterbar 1.0.5 ===============================================

问题 I have a framework target in Xcode 11.x to build a Dynamic framework with statically linking some 3rd party libraries using pod file. platform :ios, '9.0' #use_frameworks! target 'Framework' do pod 'DeviceUtil', '~> 2.0' end Now I have a requirement to build a Static framework, and for this I changed the "Mach-O' type to Static Library in 'Framework's' target build settings and able to create Static framework. The generated framework shows all architectures correctly (for architecture i386):

问题 I'm trying to create a shared library (.so file) that will include its own copy of glibc and link to it statically. I am already linking to libgcc and libstdc++ statically using -static-libgcc -static-libstdc++ in addition to -shared -fPIC and it works great. What combination of flags do I need to set to link to the static version of glibc as well? I tried adding -static to the lot but got this error: /usr/bin/ld: /home/.../x86_64-unknown-linux-gnu/4.6.2/crtbeginT.o: relocation R_X86_64_32