Kai Pastor

~~~cmake set(VCPKG_BUILD_TYPE debug) ~~~ Don't use this setup. It is unsupported. If you really want a custom debug-only single-config triplet, use the `release` type but with debug flags as needed.

> When I just use the default triplets, vcpkg+cmake seem to get confused about when to build/link debug versus release libraries. This issue is not about default triplets,

It shouldn't be disabled for linux. You also need other system development packages for building qt with vcpkg for linux.

Did you actually install the development package (Ubuntu: `libva-dev`)? And yeah, static library linkage is second-class in Qt.

I tested it now on Ubuntu, and I can confirm that `qtmultimedia[core,ffmpeg]:x64-linux` installs. The CMake config provides `Qt6::QFFmpegMediaPlugin`, and there is `Qt6/plugins/multimedia/libffmpegmediaplugin.a`.

> To build qtmultimedia with ffmpeg it needs to be built with vaapi which is not in vcpkg yet. > > https://github.com/microsoft/vcpkg/blob/742c086636a9cfb57eb77a6cc5f2d6832666d169/ports/qtmultimedia/portfile.cmake#L36-L37 Note that this generally disables vaapi in qtmultimedia...

Removing that vaapi line in the portfile (or overwriting it in the triplet file) let qtmultimedia build with system vaapi. So no matter how I try, qtmultimedia[ffmpeg]:x64-linux 6.8.1 always installs...

> **Additional context** Perhaps we need `gettext:$target` to deploy a `vcpkg-cmake-wrapper` around `FindGettext.cmake` that injects the `MSGMERGE` and `MSGFMT` executable variables from the host build. FTR, this is what I...

It should be fixed. As far as port builds are concerned: Install gettext[tools] for the host, and downstream port will have gettext tools in `PATH`. For user projects, it is...

If there is an problem at all, isn't it an upstream issue?