Using clang-analyze in Hunter build about polly HOT 4 OPEN

Should the clang-analyze script should continue to rebuild with clang after reporting warnings for a library using clang analyze?

It designed so it will stop the build with the error. The idea was to have additional toolchain in CI testing (like Travis) so one of the jobs report an error if any warning found. Then you explicitly mark the warning as ignored or fix it, and retrigger build again until you have greeny success status.

Quite the same happens if you use this toolchain in Hunter. Every package build such way, hence you see broken package.

What is the end goal? You want to analyze your current project which have 3rd parties from Hunter. Are you interested in warning from 3rd party?

from polly.

What is the end goal? You want to analyze your current project which have 3rd parties from Hunter. >Are you interested in warning from 3rd party?

Exactly this, I want to ignore the warnings from third parties and stop with an error on the package I am currently building

from polly.

Exactly this, I want to ignore the warnings from third parties and stop with an error on the package I am currently building

Okay. So the plan is to add some option/variable that can disable toolchain forwarding in Hunter. I'll think about it and let you know when it will be fixed.

As a workaround you can include analyze.cmake file with compiler settings manually without updating CMAKE_TOOLCHAIN_FILE value. Just set it after command project:

HunterGate(URL ... SHA1 ...)
project(...)
include("/path/to/polly/analyze.cmake")
add_executable(...)

If you're using build.py script pick for the --toolchain option some compatible toolchain (libcxx for example).

from polly.

As a workaround you can include analyze.cmake file with compiler settings manually without updating CMAKE_TOOLCHAIN_FILE value. Just set it after command project:

Thanks, this solves if for now!

from polly.