Nick D'Ademo

Thanks for the info! Do you have any ideas on what specifically in Qt 5.5 is making it fail?

@mohabouje Any plans to review and merge this soon?

Good work @Neumann-A ! FYI: 6.7.1 is planned to be released today: https://lists.qt-project.org/pipermail/releasing/2024-April/003016.html Though, not sure if it has been delayed or not.

@jeremy-rifkin VS: 17.8.2 vcpkg commit: `4cac260c4b7331538d31886f57739fea0bffa27e`

> Hi @nickdademo, I've added a workaround upstream and libassert builds on msvc 19.38 should work as of [b672ba2](https://github.com/jeremy-rifkin/libassert/commit/b672ba234858a819a735eb4c18a708aed12e446c) Works via vcpkg now - thanks a lot!

> Thank you for the report, I'll look into this. You shouldn't have to set the assert_DIR. Did you install with the `x64-windows-static` triplet? Dynamic build but statically linking `libassert`...

@jeremy-rifkin Seems like everything is fixed by the new vcpkg port in https://github.com/microsoft/vcpkg/pull/36745

> Awesome thanks! Is `set(assert_DIR ${VCPKG_INSTALLED_DIR}/${VCPKG_TARGET_TRIPLET}/share/libassert)` still needed? > > One way or another, I'm reworking the cmake to use `libassert` internally not `assert` for the reasons @Cazadorro pointed out...