Wholearchive windows cmake full#

But by default make would just do native build. There are wrapper-scripts for different cross-compilation targets, which just set appropriate variables and run make. Guide doesn't mention that make could be called directly. And the external dependencies with their headers would go into /tensorflow/tensorflow/lite/tools/make/downloads (for example flatbuffers headers are in /tensorflow/tensorflow/lite/tools/make/downloads/flatbuffers/include). The output library will be stored as /tensorflow/lite/tools/make/gen//lib/libtensorflow-lite.a. make -f tensorflow/lite/tools/make/Makefile The native build of all-inclusive TF Lite static library can be done very similar to official build instructions for RPi, iOS or ARM64 using plain old make:ġ./tensorflow/lite/tools/make/download_dependencies.shĢ. I tried to add a custom target to my CMakeLists.txt, which would build TF Lite with Bazel: set(TENSORFLOW_DIR $/bazel-tensorflow/external/flatbuffers/include/.

Now I want to build it as a separate project (shared library) linking to TF Lite statically and using CMake as a build system.

Wholearchive windows cmake full#

It took forever to stumble across this technique, so I'm sharing it.I've successfully built a simple C++ app running TF Lite model by adding my sources to tensorflow/lite/examples, similarly to what the official C++ TF guide suggests for full TF. Gvalue-gpsizevalue Set the maximum size of objects to be optimized using the GP register to size. Provided for compatibility with other tools. Now when I create an executable or a shared library by linking against this souce-combined library, I get the -whole-archive and -no-whole-archive as bookends around the entire set of static libraries that were the link dependencies of 'source'. This option is useful when using unmodified Unix makefiles on a Microsoft Windows host, since some versions of Windows wont run an image unless it ends in a. Target_link_libraries(source-combined PUBLIC I do not have any knowledge on CMake or C++. It worked in Linux, but for various reasons I need to run the program in Windows. Set_target_properties(source-combined PROPERTIES LINKER_LANGUAGE CXX) user984201 Asks: CMake '-Wl,-whole-archive' option for windows I am trying to build an executable of a program/project. I created 'source-combined' as follows: add_library(source-combined STATIC '') It contained actually nothing itself, but had linkage dependencies on a bunch of other static libraries. For me, the top-level static library was called 'source'. Using -whole-archive linker option with CMake and libraries with other library dependencies Ask Question Asked 4 years, 7 months ago Modified 1 year ago Viewed 18k times 17 I've got a project that used to be a giant set of source files that all got compiled and then linked as one executable. The workaround I found for versions earlier than that was to create an intermediate static library that used some property magic to place all linkage dependencies inside the -whole-archive section.

What am I doing wrong?įor 3.12 and newer versions of CMake, I would use object libraries. putting the -whole-archive stuff at lower layers), but haven't come across an approach that works using CMake. I've tried many different combinations (e.g. there is no equivalent to ld's -whole-archive). The problem is that the Visual Studio linker does not provide flags to link an entire static library (i.e. I expected that because Lib2A has Lib3* libraries as dependencies, that they would also be 'inside' the -whole-archive part of the linker command, but they show up outside. I'm on Windows, and I need a DLL composed of multiple static libraries, any of which can define dllexport functions not otherwise referenced in the DLL. The toolchain file sets up several CMake environment variables for better. Inevitably, symbols from some of the layer 3 static libraries get lost and I get missing symbol errors. Here is an example where windows builds are separated from other targets. I end up with an actual link stage command like: g++ -o Exe1 -Wl,-whole-archive libLib2A.a libLib2B.a -Wl,-no-whole-archive libLib3A.a libLib3B.a libLib3C.a When I add the below for the linking of Exe1: target_link_libraries(Exe1 -Wl,-whole-archive Lib2A Lib2B -Wl,-no-whole-archive) The problem is that I need to use -whole-archive when linking or else some symbols from the underlying libraries are not found. The numbers here show their layer in the hierarchy. Lib2A will depend on static Lib3A, lib3B, lib3C, etc. There's a hierarchy, so Exe1 will link against static libs Lib2A and Lib2B. As a first step in making the project more modular, I am breaking up the build into several smaller chunks and making them static libraries. I've got a project that used to be a giant set of source files that all got compiled and then linked as one executable.