I’m working on a fairly substantial application and need to provide part of the functionality to other teams in the company as a static library (the main reason for the static library is to prevent conflicts with potential different versions of sub-libraries or different compiler versions/options).

I’m working on a fairly substantial application and need to provide part of the functionality to other teams in the company as a static library (the main reason for the static library is to prevent conflicts with potential different versions of sub-libraries or different compiler versions/options).

I’m working on a fairly substantial application and need to provide part of the functionality to other teams in the company as a static library (the main reason for the static library is to prevent conflicts with potential different versions of sub-libraries or different compiler versions/options).

I’m working on a fairly substantial application and need to provide part of the functionality to other teams in the company as a static library (the main reason for the static library is to prevent conflicts with potential different versions of sub-libraries or different compiler versions/options).

I’m working on a fairly substantial application and need to provide part of the functionality to other teams in the company as a static library (the main reason for the static library is to prevent conflicts with potential different versions of sub-libraries or different compiler versions/options).

I’m new to CMake and I have a c++ project that I’m trying to put together using cmake, much of the code exists already with classes in nested dirs. I am able to get it all to compile with something like this

I have the following CMakeLists.txt file which configures and builds just fine.

I’m working on a CMake project with the following structure:

I’m working on a CMake project with the following structure:

First:
the development environment:Windows
IDE:vscode
when I use cmake build