Do not set MT/MD for Windows explicitly.#21
Conversation
Summary of ChangesHello @csukuangfj, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request streamlines the CMake build configuration by removing specific, hardcoded MSVC runtime library linking options. This change aims to prevent potential conflicts and enhance build system flexibility, especially for Windows environments, by allowing CMake to manage these settings more autonomously. Additionally, it includes a minor version update for the Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request correctly removes the explicit setting of the MSVC runtime library flags (/MT, /MTd) for static builds on Windows. This change reverts to CMake's default behavior, which is to use the dynamic runtime (/MD, /MDd). This is a significant improvement as it enhances compatibility with other libraries and prevents potential linking issues that arise from mixing different C++ runtimes. The version update is also noted. The changes are sound and make the build system more robust and flexible.
See also https://www.amd.com/en/developer/resources/technical-articles/2026/a-practical-approach-to-using-sherpa-onnx-production-ready-on-wi.html
Will fix onnxruntime and sherpa-onnx in separate PRs.