ZDoom

When trying to build GZDoom or Raze from source on Debian 12 I get some warnings related to "WebP" and "WebP path not found".

While building process seems to succeed, I strongly wonder about these things, which are neither documented at the wiki site.

How can I solve them? Thanks.

This is the exact message block: I already have installed packages webp and libwebp-dev.

Can someone help please?

You need to use vcpkg, or install the correct distro libraries.

vcpkg is probably going to be a lot easier. This is a guide to using it on Windows - viewtopic.php?t=78107 - it's exactly the same on Linux, other than paths being /a/single/root/filesystem and the fact that you will need to install cmake-gui separately - but other than that it will work.

Is this user @Nash effectively responsible of further windows-izing the project?
What's your problem with other OS's?

Furthermore, while using distro's own libraries has possible disadvantage of reducing portability, isn't it the very same for using Microsoft's sh*t now?
Now if built with vcpkg's libraries, there's possiblitiy that it won't properly work with other distros' library versions.

Asking as a non-coder, would it be difficult for GZDoom/Raze to have their own library version of WebP, so that it could be built statically?

sacarias wrote: ↑Sat Jan 06, 2024 11:36 am Is this user @Nash effectively responsible of further windows-izing the project?
What's your problem with other OS's?

Furthermore, while using distro's own libraries has possible disadvantage of reducing portability, isn't it the very same for using Microsoft's sh*t now?
Now if built with vcpkg's libraries, there's possiblitiy that it won't properly work with other distros' library versions.

Asking as a non-coder, would it be difficult for GZDoom/Raze to have their own library version of WebP, so that it could be built statically?

Wow there's a lot to unpack here.

> Is this user @Nash effectively responsible of further windows-izing the project?
Umm, no he is not.

> What's your problem with other OS's?
We have no problem with other OS's, and I don't particularly appreciate that accusation/assumption. Just because we use Windows primarily does not mean we hate Linux.

> Furthermore, while using distro's own libraries has possible disadvantage of reducing portability, isn't it the very same for using Microsoft's sh*t now?
Good lord. If you don't like it then don't use it. Just stick to GZDoom 4.9 or 4.10 or something from before the vcpkg integration. I'm not your babysitter and I'm not going to hand-hold you for every tiny thing that goes wrong. Just don't expect us to come running to fix bugs when something goes wrong, because we've long moved past it.

> Now if built with vcpkg's libraries, there's possiblitiy that it won't properly work with other distros' library versions.
This clearly shows you have absolutely no understanding of how vcpkg works.

> Asking as a non-coder, would it be difficult for GZDoom/Raze to have their own library version of WebP, so that it could be built statically?
Maybe, and it's a future possibility, but it requires as of yet someone to import it into the repository, and with the recent vulnerabilities discovered around that I think everyone would prefer to wait for webp's codebase to stabilise before taking on such a project. But in the long and short of things, we're trying to keep GZDoom buildable without vcpkg if you have the proper dependencies in place.

Split off a couple recent posts because they were more snark than any useful technical content. If the folks in question would like to continue the conversation productively, please feel free to post again with better attitudes.

Let's make one thing very clear here:

The only reason we even need a thing like vcpkg is the utter inability of Linux based developers to agree on a reliable standard for setting up shared libraries. GZDoom depends on a few that are an utter nightmare to build and integrate elsewhere because their developers really don't give a shit about making it easy. The main culprit is not WebP but libvpx, we either have the choice to link against an outdated custom-built version that was made by EDuke32's developers or use vcpkg to do it on Windows.

If these developers even the slightest bit cared about such issues, we could just fetch this stuff from their master repositories ourselves and all would be well.
Even with vcpkg on a completely fresh system it can take several minutes to build some of these catastrophically mishandled projects because no sane conventions were obeyed.

Indeed vcpkg helped me a lot for a couple of projects I follow