[Build] Warnings Treated as Errors in Windows Build for x86 platform on ORT Version 1.10.0 #23160
Labels
build
build issues; typically submitted using template
platform:windows
issues related to the Windows platform
Describe the issue
I am facing an issue where warnings are being treated as errors during the build process on the Windows platform targeting the x86 architecture with ONNX Runtime version 1.10.0(I need to support Windows 7-32bit). Upon investigating the build.py script, I found that the
use_dev_mode(args)
function setsonnxruntime_DEV_MODE
to ON, which seems to be causing the warnings to be treated as errors. I have not been able to find a parameter to pass to disable this behavior.I have checked the higher versions of ONNX Runtime and noticed that the compile_no_warning_as_error parameter was introduced in version 1.14.0 to address this issue. However, I am wondering if there is a way to achieve the same effect in version 1.10.0 by passing a parameter to build.bat.
As a workaround, I have tried setting
use_dev_mode(args)
to return OFF directly, which resolved my issue. However, I would like to know if there is an official parameter that can be used for this purpose in the 1.10.0 version.I have reviewed the documentation and existing issues but did not find a solution for this specific version.
I am aware of the compile_no_warning_as_error parameter in version 1.14.0, but I need a solution for version 1.10.0.
Is there a parameter that can be passed to build.bat in version 1.10.0 to treat warnings as informational messages instead of errors? Any guidance on this matter would be greatly appreciated.
Thank you for your attention to this issue.
Urgency
Low or Middle
Target platform
Windows-x86
Build script
.\build.bat --build_dir .\build --update --config RelWithDebInfo --build_shared_lib --parallel --x86 --skip_submodule_sync --cmake_generator "Visual Studio 17 2022" --enable_msvc_static_runtime
Error / output
Visual Studio Version
2022
GCC / Compiler Version
No response
The text was updated successfully, but these errors were encountered: