A better way for newest cmake version is to use target’s PUBLIC_HEADER properties. project(myproject) add_library(mylib some.c another.c) set_target_properties(mylib PROPERTIES PUBLIC_HEADER “some.h;another.h”) INSTALL(TARGETS mylib LIBRARY DESTINATION some/libpath PUBLIC_HEADER DESTINATION some/includepath ) Some ref: PUBLIC_HEADER CMake install command
Short answer: Remove Build Active Architecture Only (build setting parameter key is ‘ONLY_ACTIVE_ARCH’) from all of your static libraries’ project build settings or overwrite it with ‘NO’ like in the screenshot below: Detailed answer: The problem is that your static library ‘libCordova.a’ which you’re linking in your main app is only compiled for one architecture … Read more
Because they are libraries. Why invent a whole new vendor-specific extension for what is exactly the same thing as their already-vendor-specific libraries?
The default installed NDK doesn’t seem to have the tools required to strip binaries that have been built with ARMEABI support, so it ends up packaging the whole library, which increases the built file size substantially. I’ve found that installing the “NDK (Side by side)” tool from Android Studio -> Tools -> SDK Manager -> … Read more
This is probably a link order problem. When the GNU linker sees a library, it discards all symbols that it doesn’t need. In this case, your library appears before your .cpp file, so the library is being discarded before the .cpp file is compiled. Do this: g++ -o main.exe main.cpp -L. -lmylib or g++ -o … Read more
g++ -Wl,-Bstatic -lz -lfoo -Wl,-Bdynamic -lbar -Wl,–as-needed Will link zlib and libfoo as static, and libbar as dynamic . –as-needed will drop any unused dynamic library.
Public: The interface is finalized and meant to be used by your product’s clients. A public header is included in the product as readable source code without restriction. Private: The interface isn’t intended for your clients or it’s in early stages of development. A private header is included in the product, but it’s marked “private”. … Read more
You must define the statics in the cpp file. Log.cpp #include “Log.h” #include <ostream> string Log::theString; // <—- define static here void Log::method(string arg){ theString = “hola”; cout << theString << endl; } You should also remove using namespace std; from the header. Get into the habit while you still can. This will pollute the … Read more
Yes, an arm64 slice is there. To see it, you need to use lipo from the iOS toolchain, not from the host system (which doesn’t know about arm64): xcrun -sdk iphoneos lipo -info $(FILENAME)
Assuming you are generating a shared library, most probably what happens is that the variant of liblog4cplus.a you are using wasn’t compiled with -fPIC. In linux, you can confirm this by extracting the object files from the static library and checking their relocations: ar -x liblog4cplus.a readelf –relocs fileappender.o | egrep ‘(GOT|PLT|JU?MP_SLOT)’ If the output … Read more