Vcpkg: How do I build all required Windows Libraries with ITERATOR_DEBUG_LEVEL=0 (in debug)

[invy]

How to do it? Is there the way to control it via triplet? What runtime should I link against in this case?
Or I shouldn't do it at all, because I'm looking for trouble?

[Voskrese]

.._LEVEL=0 ?

add_definitions("-D...

[Neumann-A]

You could try
set(ENV{_CL_} "/D_ITERATOR_DEBUG_LEVEL=0")
or
set(VCPKG_C_FLAGS_DEBUG "/D_ITERATOR_DEBUG_LEVEL=0")
set(VCPKG_CXX_FLAGS_DEBUG "/D_ITERATOR_DEBUG_LEVEL=0")
in the triplet.

But it is probably not consistent across all ports.

[invy]

But it is probably not consistent across all ports.

@Neumann-A yes, this is what bothers me either.
The following question would be: how to I verify, that ports have been build consistently. Ootherwise it could end up in a disaster, because inconsistency could be noticed only in some cases and only after some surprise segfaults.

[Neumann-A]

@invy: You can check the debug build logs if the flag is in the cl call. Isn't it considered a feature in MS STL that libraries build with different _ITERATOR_DEBUG_LEVEL won't link due to the famous linker error. Here is just one example: https://github.com/conan-io/conan/issues/1341

[invy]

@Neumann-A they won't if you link statically, but dynamically everything would link fine.

[JackBoosY]

I think you should set it into here.

[invy]

@JackBoosY this looks good.
Will toolchain settings also affect libraries built with msbuild and automake?

[Neumann-A]

I think you should set it into here.

The correct way to do it use a custom triplet and specific a toolchain via VCPKG_CHAINLOAD_TOOLCHAIN_FILE

https://vcpkg.readthedocs.io/en/latest/users/triplets/

but it should be enough to

set(VCPKG_C_FLAGS_DEBUG "/D_ITERATOR_DEBUG_LEVEL=0")
set(VCPKG_CXX_FLAGS_DEBUG "/D_ITERATOR_DEBUG_LEVEL=0")

in a custom triplet

[invy]

@Neumann-A great!
It would be cool if I also could somehow add a custom linter :)

[JackBoosY]

@invy Does this issue solved?

[JackBoosY]

Please reopen this issue if it still bother you.