Ensure standard-conformant builds about gui_starter_template HOT 3 CLOSED

Clang-cl is new to me, so please take anything I say with a big grain of salt.

I had a look at the the llvm docs for supported command-line options (https://clang.llvm.org/docs/UsersManual.html#id9), and it sounds to me like the options they support are a subset of the full MSVC command-line options list. The docs provide a full listing of the options supported, and /permissive- is not on it.

A direct quote:

"Please file a bug for any valid cl.exe flags that clang-cl does not understand."

How would you achieve the desired result?

I would do two things:

1. File the bug report. The old adage "it's not the compiler, it's you" should not apply to clang-cl.exe, because it's a compatibility layer, not a compiler. Until the bug is fixed, clang-cl.exe will not do the job you want it to.
2. Use multiple builds to make sure you're getting all the warnings you need. To get the /permissive- flag, I would use the standard Visual Studio cl.exe compiler until clang-cl.exe is patched. To my knowledge, cl.exe can warn for things that gcc and clang cannot: See Cpp Weekly #46. Additionally, I would compile regularly with clang and gcc as well: this is what the Travis-CI, Appveyor and Github-Actions builds are for.

from gui_starter_template.

Thanks David, that is very helpful information.

I filed the bug; hopefully it'll be easy to fix.

I like the idea of having builds for each supported platform. That is probably the best way to go, in any case.

As this issue is not found about the cpp_starter_project, I am closing it.

from gui_starter_template.

No problem, thank you for filing the bug with llvm!

from gui_starter_template.