Since nobody else has come up with an answer yet, I will give it a try. Unfortunately, I don’t know that Code::Blocks IDE so my answer will only be partial. 1 How to Create a Statically Linked Executable with GCC This is not IDE specific but holds for GCC (and many other compilers) in general. … Read more
CMake favours passing the full path to link libraries, so assuming libbingitup.a is in ${CMAKE_SOURCE_DIR}, doing the following should succeed: add_executable(main main.cpp) target_link_libraries(main ${CMAKE_SOURCE_DIR}/libbingitup.a)
Open ios/YourAppName.xcodeproj in Xcode Right-click on Your App Name in the Project Navigator on the left, and click New File… Create a single empty Swift file to the project (make sure that Your App Name target is selected when adding) when Xcode asks, press Create Bridging Header and do not remove Swift file then. re-run … Read more
Given the most simple working example I can think of: 2 classes, a and b, where a depends on b . . a.h #ifndef A_H #define A_H class aclass { public: int method(int x, int y); }; #endif a.cpp #include “a.h” #include “b.h” int aclass::method(int x, int y) { bclass b; return x * b.method(x,y); … Read more
There are legitimate uses of –whole-archive when linking executable with static libraries. One example is building C++ code, where global instances “register” themselves in their constructors (warning: untested code): handlers.h typedef void (*handler)(const char *data); void register_handler(const char *protocol, handler h); handler get_handler(const char *protocol); handlers.cc (part of libhandlers.a) typedef map<const char*, handler> HandlerMap; HandlerMap … Read more
What am I doing wrong? Nothing. It sounds like your GCC is configured to build -pie binaries by default. These binaries really are shared libraries (of type ET_DYN), except they run just like a normal executable would. So your should just run your binary, and (if it works) not worry about it. Or you could … Read more
Simply pass -Wl,–exclude-libs,ALL to gcc This will tell the linker to transform all the symbols in the static libraries to hidden. –exclude-libs also accepts a list of archives (i.e. static library names) for finer granularity on which libraries to hide symbols from. Note: this will only work in systems using GNU binutils (e.g. Linux) or … Read more
you can use libtool to do it libtool -static -o new.a old1.a old2.a
If you want to remove the support for any architecture, for example, ARMv7-s in your case, use menu Project -> Build Settings -> remove the architecture from “valid architectures”. You can use this as a temporary solution until the library has been updated. You have to remove the architecture from your main project, not from … Read more
Assuming you’re talking about a static library, DUMPBIN /SYMBOLS shows the functions and data objects in the library. If you’re talking about an import library (a .lib used to refer to symbols exported from a DLL), then you want DUMPBIN /EXPORTS. Note that for functions linked with the “C” binary interface, this still won’t get … Read more