You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For CMake case
I'm not sure how you using your library on developers PCs. But it is very inconvenient that install library file path are same for debug and release configurations.
When using MSVC toolchains using Visual Studio or Ninja Multi-Config compiled library bonded to either Visual C++ Release or Debug DLLs. So to use library I have to use different CMAKE_INSTALL_PREFIX for your library and then use its different paths for debug and release configurations. It is not very convenient for non expert developers.
I think that you should use different library name suffix for debug version of installed library as commonly used in popular libraries like Qt, OpenCV, VTK and etc.
In you install rules section in CMakeLists.txt you should add following lines:
Clients of libraries can use single install path of library within their IDEs. For example settings.json in Visual Studio Code could contains following configuration:
Then developer could easily switch between debug and release configurations without worrying about Visual C++ DLLs versions.
VS 2019 have GUI editor for specifying CMake paths same as Qt Creator.
The text was updated successfully, but these errors were encountered:
For CMake case
I'm not sure how you using your library on developers PCs. But it is very inconvenient that install library file path are same for debug and release configurations.
When using MSVC toolchains using Visual Studio or Ninja Multi-Config compiled library bonded to either Visual C++ Release or Debug DLLs. So to use library I have to use different
CMAKE_INSTALL_PREFIX
for your library and then use its different paths for debug and release configurations. It is not very convenient for non expert developers.I think that you should use different library name suffix for debug version of installed library as commonly used in popular libraries like Qt, OpenCV, VTK and etc.
In you install rules section in
CMakeLists.txt
you should add following lines:So there will be two libraries:
Clients of libraries can use single install path of library within their IDEs. For example
settings.json
in Visual Studio Code could contains following configuration:Then developer could easily switch between debug and release configurations without worrying about Visual C++ DLLs versions.
VS 2019 have GUI editor for specifying CMake paths same as Qt Creator.
The text was updated successfully, but these errors were encountered: