Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[gtk] update to 4.4.0 #20654

Merged
merged 18 commits into from
Nov 29, 2021
Merged

[gtk] update to 4.4.0 #20654

merged 18 commits into from
Nov 29, 2021

Conversation

Berrysoft
Copy link
Contributor

It should also fix #20241 according to my test on Windows.

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

This is a new experimental fast check for PR issues. Please let us know if this bot is helpful!

All manifest files must be formatted

./vcpkg format-manifest ports/*/vcpkg.json

Diff
diff --git a/ports/gtk/vcpkg.json b/ports/gtk/vcpkg.json
index 3bd4af4..d045461 100644
--- a/ports/gtk/vcpkg.json
+++ b/ports/gtk/vcpkg.json
@@ -32,4 +32,4 @@
     "pango",
     "sassc"
   ]
-}
\ No newline at end of file
+}
After committing all other changes, the version database must be updated
git add -u && git commit
git checkout 973a7d517c09c8cfb7e6a548fcc260ca34ba7b60 -- versions
./vcpkg x-add-version --all
Diff
diff --git a/versions/g-/gtk.json b/versions/g-/gtk.json
index 24c1a71..31b7038 100644
--- a/versions/g-/gtk.json
+++ b/versions/g-/gtk.json
@@ -1,7 +1,7 @@
 {
   "versions": [
     {
-      "git-tree": "f1f197e3b94a55d5cbfaae2498f991a0ae733b32",
+      "git-tree": "7a0b64ed1aad48778c783587ead610d7368ee580",
       "version": "4.4.0",
       "port-version": 0
     },

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

This is a new experimental fast check for PR issues. Please let us know if this bot is helpful!

After committing all other changes, the version database must be updated
git add -u && git commit
git checkout 973a7d517c09c8cfb7e6a548fcc260ca34ba7b60 -- versions
./vcpkg x-add-version --all
Diff
diff --git a/versions/g-/gtk.json b/versions/g-/gtk.json
index e13b293..31b7038 100644
--- a/versions/g-/gtk.json
+++ b/versions/g-/gtk.json
@@ -1,7 +1,7 @@
 {
   "versions": [
     {
-      "git-tree": "9e7905845335a944321446ecd346ff7b3e154a47",
+      "git-tree": "7a0b64ed1aad48778c783587ead610d7368ee580",
       "version": "4.4.0",
       "port-version": 0
     },

@JonLiu1993 JonLiu1993 added the category:port-update The issue is with a library, which is requesting update new revision label Oct 11, 2021
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

This is a new experimental fast check for PR issues. Please let us know if this bot is helpful!

After committing all other changes, the version database must be updated
git add -u && git commit
git checkout 973a7d517c09c8cfb7e6a548fcc260ca34ba7b60 -- versions
./vcpkg x-add-version --all
Diff
diff --git a/versions/g-/gtk.json b/versions/g-/gtk.json
index 31b7038..3592b00 100644
--- a/versions/g-/gtk.json
+++ b/versions/g-/gtk.json
@@ -1,7 +1,7 @@
 {
   "versions": [
     {
-      "git-tree": "7a0b64ed1aad48778c783587ead610d7368ee580",
+      "git-tree": "770f1bccb962223beac9a40b7069d2ae414b068c",
       "version": "4.4.0",
       "port-version": 0
     },

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

This is a new experimental fast check for PR issues. Please let us know if this bot is helpful!

After committing all other changes, the version database must be updated
git add -u && git commit
git checkout 973a7d517c09c8cfb7e6a548fcc260ca34ba7b60 -- versions
./vcpkg x-add-version --all
Diff
diff --git a/versions/g-/gtk.json b/versions/g-/gtk.json
index 31b7038..7dac5e1 100644
--- a/versions/g-/gtk.json
+++ b/versions/g-/gtk.json
@@ -1,7 +1,7 @@
 {
   "versions": [
     {
-      "git-tree": "7a0b64ed1aad48778c783587ead610d7368ee580",
+      "git-tree": "e6e7ce0da8740be9a4fa16e0245a35ff16a185b6",
       "version": "4.4.0",
       "port-version": 0
     },

@Berrysoft
Copy link
Contributor Author

Berrysoft commented Oct 11, 2021

There seems to be no xdamage extension in the CI image, so I modified the meson.build to adapt to that. However, it seems that the GTK developers require the package to be available. Are there some ways to add xdamage to the CI Linux image?

@JackBoosY
Copy link
Contributor

JackBoosY commented Oct 12, 2021

cc @BillyONeal to add xdamage in the next roll if it's suitable.

@JackBoosY JackBoosY added the depends:vm-update PR contains changes to the VM provisioning scripts label Oct 12, 2021
ports/gtk/0003-vs2022-rc.patch Outdated Show resolved Hide resolved
ports/gtk/0005-xdamage-optional.patch Outdated Show resolved Hide resolved
@BillyONeal
Copy link
Member

There seems to be no xdamage extension in the CI image, so I modified the meson.build to adapt to that. However, it seems that the GTK developers require the package to be available. Are there some ways to add xdamage to the CI Linux image?

@BillyONeal ➜ /workspaces/vcpkg-tool (main) $ sudo apt install xdamage
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package xdamage

Please provide a patch to scripts/azure-pipelines/linux/provision-image.sh that adds what you need.

@Berrysoft
Copy link
Contributor Author

The package should be libxdamage-dev. I'll try it.

@JackBoosY JackBoosY added depends:different-pr This PR or Issue depends on a PR which has been filed and removed requires:author-response labels Nov 12, 2021
@cenit
Copy link
Contributor

cenit commented Nov 19, 2021

what's blocking this PR?
if a rebuild is triggered it should pass easily. It passed in my own #20658

@cenit
Copy link
Contributor

cenit commented Nov 19, 2021

@JackBoosY this PR does not depend anymore on other PRs

@Berrysoft
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Commenter does not have sufficient privileges for PR 20654 in repo microsoft/vcpkg

@Berrysoft
Copy link
Contributor Author

Well, then... we need a rerun @JackBoosY

@cenit
Copy link
Contributor

cenit commented Nov 19, 2021

you can merge with master and trigger a rebuild in that way

@PhoebeHui
Copy link
Contributor

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@JackBoosY JackBoosY added info:reviewed Pull Request changes follow basic guidelines and removed depends:different-pr This PR or Issue depends on a PR which has been filed labels Nov 22, 2021
@@ -1,5 +1,5 @@
-#include <winuser.h>
-#include <winver.h>
+#define WIN32_LEAN_AND_MEAN
Copy link
Member

Choose a reason for hiding this comment

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

Has this patch been submitted upstream? I don't think it is a correct fix. The problem is that rc.exe is being handed a huge blob of C header files it is not intended to tolerate, and I think the correct fix is that all such things should be guarded by RC_INVOKED; but at a minimum upstream needs to be made aware and OK this as they seem relatively responsive.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Well, it has been merged: https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/4063

I don't know how the headers affect rc.exe, but at least it works...

Copy link
Contributor Author

@Berrysoft Berrysoft Nov 23, 2021

Choose a reason for hiding this comment

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

Oh, and by the way, the merged patch is not authored by me. Mine was closed in perfer of the merged one.

help='require admin access to application')
parser.add_argument('--input-resource-file', dest='resource',
default=None,
- help='existing .rc file to embed UAC manifest (do not generate a new .rc file), must have included winuser.h in it')
Copy link
Member

Choose a reason for hiding this comment

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

Seems like this part of the change is unintended?

Copy link
Contributor Author

@Berrysoft Berrysoft Nov 23, 2021

Choose a reason for hiding this comment

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

Hm, seems so. This is only a diff, and git might see something we could not found.

Copy link
Contributor

Choose a reason for hiding this comment

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

So, please revert this changes.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Oh, I finally found the difference. winuser.h was changed to windows.h, because of the headers included changed above.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think the changes should not be reverted then, although it doesn't make effects to our end users.

Copy link
Contributor

Choose a reason for hiding this comment

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

So I think it's good.
Ping @BillyONeal for review again.

Copy link
Member

Choose a reason for hiding this comment

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

Ah, I see. The change is unrelated to how it builds in vcpkg which means we would normally want to keep it out of a vcpkg patch, but it's here because of the corresponding upstream change.

@BillyONeal BillyONeal added depends:upstream-changes Waiting on a change to the upstream project requires:author-response and removed info:reviewed Pull Request changes follow basic guidelines labels Nov 22, 2021
Copy link
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.

Waiting for notification that upstream has been notified about the patch and the lines that look like an unrelated whitespace change removed. (We don't need to wait until upstream has done a release with the changes, but we want to give them some opportunity to either accept or reject them since this is effectively putting code in their mouth)

@JackBoosY JackBoosY removed the depends:upstream-changes Waiting on a change to the upstream project label Nov 23, 2021
@BillyONeal BillyONeal added the info:reviewed Pull Request changes follow basic guidelines label Nov 29, 2021
@BillyONeal
Copy link
Member

Thanks for providing the link to the upstream change :)

@BillyONeal BillyONeal merged commit 3f56cc6 into microsoft:master Nov 29, 2021
@BillyONeal
Copy link
Member

Thanks for the update!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:port-update The issue is with a library, which is requesting update new revision info:reviewed Pull Request changes follow basic guidelines
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[gtk] build failure
9 participants