va_win32: Fix debug build break

[sivileri]

Fix debug build break:

[3/9] Compiling C object va/va_win32.dll.p/win32_va_win32.c.obj
FAILED: va/va_win32.dll.p/win32_va_win32.c.obj
"cl" "-Iva\va_win32.dll.p" "-Iva" "-I..\va" "-I." "-I.." "/MDd" "/nologo" "/showIncludes" "/utf-8" "/W2" "/Od" "/Zi" "-DLIBVA_MAJOR_VERSION=2" "/Fdva\va_win32.dll.p\win32_va_win32.c.pdb" /Fova/va_win32.dll.p/win32_va_win32.c.obj "/c" ../va/win32/va_win32.c
../va/win32/va_win32.c(186): error C2231: '.LowPart': left operand points to 'struct', use '->'
../va/win32/va_win32.c(186): error C2231: '.HighPart': left operand points to 'struct', use '->'
../va/win32/va_win32.c(188): error C2231: '.LowPart': left operand points to 'struct', use '->'
../va/win32/va_win32.c(188): error C2231: '.HighPart': left operand points to 'struct', use '->'
[5/9] Compiling C object va/va.dll.p/va_trace.c.obj
ninja: build stopped: subcommand failed.

Fixes: 484f128 ("win32: remove duplicate adapter_luid entry")

CC @dvrogozh @evelikov @XinfengZhang

[dvrogozh]

looks good

[evelikov]

Ouch, sorry about that. Should we add a debug build combination to the CI matix?

[sivileri]

Ouch, sorry about that. Should we add a debug build combination to the CI matix?

No worries :). Maybe adding a new combination with -Dbuildtype=debug for the meson setup args to https://github.com/intel/libva/blob/master/.github/workflows/windows.yml ?

[dvrogozh]

Maybe adding a new combination with -Dbuildtype=debug for the meson setup args to https://github.com/intel/libva/blob/master/.github/workflows/windows.yml ?

Yes. CI coverage would be nice to have to avoid anything similar in the future.