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
I noticed that that commands with a value like this:
--shading-language hlsl
No longer work with MSVC in release builds only and we get an ExtrasError instead:
CLI11 Parse Error: [sample] The following arguments were not expected: hlsl --shading-language
A debug or release with debug info build works fine.
I tried to debug, which is kinda hard if it works in all builds with debug information and I'm out of clues. Updating to the latest version of CLI11 didn't help either.
Any ideas as to why this could happen, and why only in release mode?
The text was updated successfully, but these errors were encountered:
Bisecting might take some time, but I went back as far as tag v1.9.0 and the issue still persists. So I guess this is an issue on our side, but that code was written by a different maintainer. Any hints as to where I could look for the cause of that problem only showing up in release?
If it predates 2.0 then that is a different matter, I was worried one of the recent fixes changed something. I will have to dig into it a bit more on exactly how you are using things. Do you have the exact compiler flags you are using to generate the error?
We use this library for command line parsing in our Vulkan samples at https://github.com/KhronosGroup/Vulkan-Samples
I noticed that that commands with a value like this:
--shading-language hlsl
No longer work with MSVC in release builds only and we get an ExtrasError instead:
CLI11 Parse Error: [sample] The following arguments were not expected: hlsl --shading-language
A debug or release with debug info build works fine.
I tried to debug, which is kinda hard if it works in all builds with debug information and I'm out of clues. Updating to the latest version of CLI11 didn't help either.
Any ideas as to why this could happen, and why only in release mode?
The text was updated successfully, but these errors were encountered: