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
Currently, the integration of vcpkg into msbuild only has the following behaviors:
Automatically add installed/TRIPLET/include to the additional include directory.
Automatically link installed/TRIPLET/debug/lib or installed/TRIPLET/lib to additional dependencies.
Automatically find the used libraries according to the link log and copy them to the output directory in the post build step.
This does not match the behavior of cmake integration:
additional macros
additional paths
other configuration processes
may be added to the cmake configuration file.
So can we analyze these items based on the generated cmake configuration files and add them to the msbuild integration?
How to add?
How to identify the library used?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Currently, the integration of vcpkg into msbuild only has the following behaviors:
This does not match the behavior of cmake integration:
may be added to the cmake configuration file.
So can we analyze these items based on the generated cmake configuration files and add them to the msbuild integration?
How to add?
How to identify the library used?
Beta Was this translation helpful? Give feedback.
All reactions