@talisein Is there a good reason your libxml2.wrap file downloads a released version
of libxml2? Other wrap files download the latest version from the git repo. See e.g.
https://gitlab.gnome.org/GNOME/gtkmm/-/tree/master/subprojects

@fanc999 Can you have a look at this PR, please.

There's still no meson.build in libxml2 but it seems like someone is starting: https://gitlab.gnome.org/GNOME/libxml2/-/issues/328

Hi @kjellahl,

Sorry for the delay, I think other than the comment I had I think we are fine with this. I'm not a big fan of static builds, but I think otherwise things seemed to be fine with me.

Hi @talisein,

I think the other alternative to use the latest libxml2 version is to use the CMake method, since libxml2 does have a CMake build system.1 Maybe we want to split up this PR into 2, one for the static builds of libxml++, and the other for adding a fallback for libxml2.

With blessings, and cheers!

Maybe we want to split up this PR into 2, one for the static builds of libxml++, and the other for adding a fallback for libxml2.

@talisein Yes, it would be fine to split this up. At least separate commits
for enabling static builds and for having libxml2 as a subproject. They are
two unrelated features, aren't they?

Sure I'll split it up. Its there for the convenience of the github CICD workflow.

I've split this PR up:

• Allow static linking on Windows #29 The static bits are here.
• meson: Add libxml2 cmake wrap #30 libxml2 wrap

Once those two merge I'll open a PR to add the windows workflow

Hi @talisein,

Thanks, I think this PR looks fine to me at this point.