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, our build system relies on CMake code originally generated by Visual Studio. I have attempted multiple times to add clang-cl as a build target and failed, so I think moving to Make (of which I am familiar with GNU Make) or writing custom code for CMake to configure the build system might make it easier to manage it later. Of course, if we work with CMake, that would allow us to use Ninja, and switching to something else might make it difficult to use MSVC's Hot Reload feature. I think that if the feature is only available through Visual Studio's debugger, then it doesn't matter.
documentationImprovements or additions to documentationenhancementNew feature or requestquestionFurther information is requested
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
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, our build system relies on CMake code originally generated by Visual Studio. I have attempted multiple times to add
clang-cl
as a build target and failed, so I think moving to Make (of which I am familiar with GNU Make) or writing custom code for CMake to configure the build system might make it easier to manage it later. Of course, if we work with CMake, that would allow us to use Ninja, and switching to something else might make it difficult to use MSVC's Hot Reload feature. I think that if the feature is only available through Visual Studio's debugger, then it doesn't matter.Beta Was this translation helpful? Give feedback.
All reactions