Skip to content

[glibmm] Update to 2.86.0#51067

Open
SchaichAlonso wants to merge 6 commits intomicrosoft:masterfrom
SchaichAlonso:51066-update-glibmm-to-2.86.0
Open

[glibmm] Update to 2.86.0#51067
SchaichAlonso wants to merge 6 commits intomicrosoft:masterfrom
SchaichAlonso:51066-update-glibmm-to-2.86.0

Conversation

@SchaichAlonso
Copy link
Copy Markdown
Contributor

Fixes #51066.

  • Changes comply with the maintainer guide.
  • SHA512s are updated for each updated download.
  • The "supports" clause reflects platforms that may be fixed by this new version, or no changes were necessary.
  • Any fixed CI baseline and CI feature baseline entries are removed from that file, or no entries needed to be changed.
  • All patch files in the port are applied and succeed.
  • The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
  • Exactly one version is added in each modified versions file.

@BillyONeal
Copy link
Copy Markdown
Member

Build fails with

..\src\glibmm-2-ccf2fc67d7.clean\glib\meson.build:28:4: ERROR: Problem encountered: Static builds are not supported by MSVC-style builds

so it seems like this should use "supports".

```
..\src\glibmm-2-ccf2fc67d7.clean\glib\meson.build:28:4: ERROR: Problem encountered: Static builds are not supported by MSVC-style builds
```
Copy link
Copy Markdown
Member

@BillyONeal BillyONeal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@BillyONeal BillyONeal marked this pull request as draft April 10, 2026 00:40
@SchaichAlonso SchaichAlonso force-pushed the 51066-update-glibmm-to-2.86.0 branch from 3b873b7 to f6190d9 Compare April 10, 2026 08:39
@SchaichAlonso
Copy link
Copy Markdown
Contributor Author

SchaichAlonso commented Apr 10, 2026

I've added the static windows combination to the (un)supported list.

The failing ci pipelines are already marked to fail in ci.baseline.txt:L244~246, raising the question why the CI is reporting it though.

@SchaichAlonso SchaichAlonso force-pushed the 51066-update-glibmm-to-2.86.0 branch from f6190d9 to 2a71085 Compare April 10, 2026 09:23
@SchaichAlonso SchaichAlonso force-pushed the 51066-update-glibmm-to-2.86.0 branch from 2a71085 to 117ac6d Compare April 10, 2026 09:25
…nso/vcpkg into pr-51067-glibmm

# Conflicts:
#	ports/glibmm/vcpkg.json
#	versions/g-/glibmm.json
@BillyONeal
Copy link
Copy Markdown
Member

The failing ci pipelines are already marked to fail in ci.baseline.txt:L244~246, raising the question why the CI is reporting it though.

It was in ci.baseline.txt but not ci.feature.baseline.txt. With the updated supports things now fail because the check complains about the baseline(s) duplicating something already implied by a "supports".

I fixed this for you in SchaichAlonso#2

@BillyONeal BillyONeal marked this pull request as ready for review April 11, 2026 18:49
Copy link
Copy Markdown
Member

@BillyONeal BillyONeal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@BillyONeal BillyONeal enabled auto-merge (squash) April 11, 2026 18:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[glibmm] update to 2.86.0

2 participants