static-linking

I'd like to link libpng found by pkg-config statically. pkg-config --libs --static libpng outputs -L/usr/local/Cellar/libpng/1.6.15/lib -lpng16 -lz I have both libpng16.a libpng16.dylib in that directory, and if I use these flags the library gets linked dynamically. How can I tell either pkg-config or the linker (preferably in some portable-ish way) that I really want it linked statically? I've tried adding -static before pkg-config's flags, but that makes clang's ld try and fail to link "crt0.o". The pkg-config --static option relies on proper tagging in the .pc files . If providing the -

I have a C++ compiled static library of about 15 classes and their member functions and stuff, and compiled, it's almost 14 megabytes. It links to Google's dense hash table library and MPIR, which is like GMP for Windows, but I did that in a plain exe and it was a few kilobytes. Why is it so massive? What can I do to reduce its size? It seems like there's other programs which are far more complicated than mine that are far smaller. Compiled with Visual C++, command line is: /Zi /nologo /W3 /WX- /O2 /Oi /Oy- /GL /D "WIN32" /D "NDEBUG" /D "_CONSOLE" /D "_UNICODE" /D "UNICODE" /Gm- /EHsc /GS /Gy

I have been cross-compiling some Linux tools (and some of my own C code) to Android and one of the challenges that I face is that Android's libc has some missing/stripped components and I end up patching my code to make it work with Android's libc (for e.g. a problem like this http://credentiality2.blogspot.com/2010/08/compile-ncurses-for-android.html ) Q1 : How do I go about statically linking against glibc (and other dependencies) while cross-compiling with the arm toolchain (or ndk-build)? Q2 : Is it a good idea to statically link against glibc for binaries for Android? Should I expect

I am trying to use a library I've compiled myself in an iOS app. The library is the Tesseract OCR lib. It seems like compiling that (and its dependencies) have gone ok. However, when I try to link against this lib in my app project, the app fails to link. The link errors surprise me; it seems like there are problems with the Tesseract stuff finding pretty standard C++ stuff. Any suggestions about what I might be doing wrong would be most helpful. Here is a snippet of the kind of link errors I'm seeing. Undefined symbols for architecture armv7: "std::string::find_last_of(char const*, unsigned

I need to create a shared library whose own dependencies including libc/libstdc++ have to be statically linked to it to produce a self-contained binary. I tried to do this g++ -c -fpic -o foo.o foo.cpp g++ -static -shared -o foo.so foo.o which fails with: /usr/bin/ld.bfd.real: /usr/local/lib/gcc/x86_64-unknown-linux-gnu/5.2.0/crtbeginT.o: relocation R_X86_64_32 against `__TMC_END__' can not be used when making a shared object; recompile with -fPIC /usr/local/lib/gcc/x86_64-unknown-linux-gnu/5.2.0/crtbeginT.o: could not read symbols: Bad value collect2: error: ld returned 1 exit status Can

I have C program I compile with mingw on Windows. It works fine but requires MSVCRT.DLL . I want to link that statically (like I can do in Visual Studio). Is this possible? I tried -static flag to gcc and it didn't make any change. What about C++ program using also standard C++ library? I believe that MinGW doesn't use the static runtime library for copyright reasons. You can maybe try to use newlib ( http://sourceware.org/newlib/ ) to create an executable that doesn't link to msvcrt.dll Having spent a while searching for this myself, I came across this post introducing the in-progress Mingw32

I wrote simple apps with Openssl in C and C++. I compile them like this: gcc openssltest.c -o openssltest -lcrypto g++ openssltest.cpp -o openssltest -lcrypto And its all ok but only, when you have Openssl installed. I would like to compile it that I can run them on OS where theres no Openssl installend (linux-like OS). I tried this: gcc -c openssltest.c -lcrypto -static gcc openssltest.o -o openssltest -lcrypto -static and same for C++: g++ -c openssltest.cpp -lcrypto -static g++ openssltest.o -o openssltest -lcrypto -static But have those errors: /usr/lib/gcc/x86_64-linux-gnu/4.7/../../..