The reasons given in other answers are correct, but they are not the most important reason. The most important reason why glibc should not be statically linked, is that it makes extensive internal use of dlopen, to load NSS (Name Service Switch) modules and iconv conversions. The modules themselves refer to C library functions. If … Read more
If you want to distribute a combined work, you’ll have to use the following license; Proprietary Source code + GPL Source code Either static or dynamically linked: You must release both parts as GPL. Proprietary Source code + LGPL Source code statically linked: Either you must release both parts as LGPL. Or provide everything that … Read more
I figured out what caused the problem. I changed ‘Build Active Architecture Only’ of TapkuLibrary from Yes to No and it compiles with no problem.
I did some investigation and although I could not find a satisfying solution to the problem, I did find a half-solution. The problem of static builds boils down to 3 things: Building and linking the project’s internal libraries. Pretty simple, one just has to flip the BUILD_SHARED_LIBS switch OFF. Finding static versions of external libraries. … Read more
It can be either. Only iOS8+ will allow dynamic frameworks in the app bundle, however. The way to find out is to look in the .framework and use the file command on the main file: $ cd iOS/Crashlytics.framework $ ls -l total 9984 -rwxr-xr-x 1 andy staff 4710656 11 Sep 17:11 Crashlytics drwxr-xr-x 8 andy … Read more
If your toolchain includes the static winpthreads, adding the option -static Will pull in static versions of all libraries it can. Alternatively, you can remove libwinpthread.dll.a and the DLL itself from the toolchain directories. This might mess up programs linking with libstdc++ and libgcc DLLs though, so be careful. A third option is to use … Read more
There doesn’t seem to be any mention of any equivalent pragmas in the GCC manual’s page on pragmas. One reason I saw for GCC not supporting linking in source code was that sometimes, correct linking depends on link order; and this would require you to make sure that the linking order happens correctly no matter … Read more
See question 3544035. Also discussed here and there. It depends on what use you will have for your static library. If you only want to link it into programs, it doesn’t need PIC code (libtool calls that a convenience library, because you could pretty much do without it, it simply helps get your compilation process … Read more
Since Rust 1.19, you can statically link the C runtime (CRT) to avoid this very common situation on Windows: The program can’t start because VCRUNTIME140.dll is missing from your computer. Try reinstalling the program to fix this problem. Add this to your .cargo/config file, using the appropriate target triple for your platform: [target.x86_64-pc-windows-msvc] rustflags = … Read more
I think this is very annoying, and I think it is arrogant to call a feature “useless” because it has problems dealing with certain use cases. The biggest problem with the glibc approach is that it hard-codes paths to system libraries (gconv as well as nss), and thus it breaks when people try to run … Read more