Update the vcpkg port for magnum-integration

[zmoote]

I am having a build error for the magnum-integration vcpkg port on Windows.

According to the user Mengna-Li, "The upstream has already fixed this issue, magnum-integration need to update to latest version." (See here)

[mosra]

The last tagged release is from five years ago (sorry about that, more info in mosra/corrade#197 and mosra/magnum#453), but if you install --head of all packages it should work I think. Details in docs.

[zmoote]

The last tagged release is from five years ago (sorry about that, more info in mosra/corrade#197 and mosra/magnum#453), but if you install --head of all packages it should work I think. Details in docs.

Thank you. But what about if I'm using vcpkg with manifest mode rather than classic mode? From what I understand, passing the --head flag only works with the classic mode. Is there a workaround for manifest mode?

[mosra]

I don't have a solution for that right now, sorry.

The vcpkg packages were always maintained by the community, and over the years all people who took care of them switched away from vcpkg for one reason or another so there's basically nobody who'd do regular updates anymore. Mostly because vcpkg was just too finicky to deal with, its PR review process too demanding, and because Magnum is developed in a more of a "rolling release" model where master is always stable rather than regular tagged versions. So the packages are increasingly falling behind, with several new features and plugins not even exposed there.

If you use CMake for your project, you could switch to using vcpkg just for Magnum's dependencies (say, SDL / GLFW, libpng and such), and have Magnum integrated as a CMake subproject or via FetchContent / CPM for example. Compared to Vcpkg you'll have the full control over which revision you're on and which features and plugins you have enabled, without relying on a perpetually outdated package definition.

[zmoote]

Okay, thank you!

[mosra]

I got an idea how to make the versioning in vcpkg work with my glacial pace of tagged releases, so reopening this until it's actually fixed in the vcpkg package.