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

Update glfw package to 3.3.4 #479

Merged
merged 1 commit into from
Nov 15, 2021
Merged

Conversation

alex-tdrn
Copy link

I've followed this guide step by step carefully. [Yes]

VERSION
"3.3.4-p0"
URL
"https://github.com/cpp-pm/glfw/TODO"

Choose a reason for hiding this comment

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

https://github.com/cpp-pm/glfw/archive/refs/tags/v3.3.4-p0.tar.gz
with SHA1 68860fe3983bef0c73c21d23cc69c8aac9cf493c

Copy link
Author

Choose a reason for hiding this comment

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

I accidentally pushed an older branch, my bad

Choose a reason for hiding this comment

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

no worries ;)

@alex-tdrn alex-tdrn force-pushed the pr.update_glfw_3_3_4 branch 2 times, most recently from 20d4a96 to 469926e Compare October 28, 2021 06:35
@NeroBurner
Copy link

LGTM, let's see what the CI has to say

@alex-tdrn
Copy link
Author

alex-tdrn commented Oct 28, 2021

I've made a mistake while rebasing the hunter patches, I rebased on top of the starting commit for 3.3.4, instead of the release commit (don't ask me how I managed to do that haha). I'm going to fix that, and keep running the test matrix on my hunter fork until all toolchains pass, I'll update this pr then ✌️

Sidenote: the 3 failing toolchains also fail on the 3.3.0 version of glfw, currently in hunter
I will try to do some "light" hunterization instead of the original 20 patches, meaning I will only add hunter_add_package calls where relevant and not modify the script logic too much otherwise, and see where that gets us

EDIT: The rebase is correct, but I'm still going to try to make the remaining toolchains work, with the original 20 patches as they seem to be necessary and smarter people than me have thought them out

@alex-tdrn
Copy link
Author

I've removed the iOS and Android builds from the build matrix, since glfw does not support mobile platforms at the moment. The last failing build seems to originate from xcb, and indeed, the analyze build is failing for xcb as well (on current master).

As a sidenote, a 3.3.5 tag was created upstream 2 hours ago, it looks like another release is coming, should we wait a bit and skip directly to that release instead?

@NeroBurner
Copy link

I think you should keep the failing jobs in the build matrix, as they are used for documentational purposes (there's a website listing the build status for the packages)

As for waiting, just add this version and when the next one is released add the new version instead of potentially waiting and waiting

@NeroBurner
Copy link

ah yes here it is: Per package testing table

PACKAGE_NAME
glfw
VERSION
"3.3.4-p0"
Copy link
Member

Choose a reason for hiding this comment

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

Can you remove this version, if it isn't useful?

Copy link
Author

Choose a reason for hiding this comment

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

I've deleted the p1 tag, and pointed the p0 tag to the latest glfw commit on the 3.3.4 branch now

@NeroBurner
Copy link

NeroBurner commented Nov 10, 2021

@alex-tdrn could you rebase and squash the changes, otherwise LGTM

Remove Android and iOS from build matrix

GLFW does not support mobile platforms yet
glfw/glfw#1726

Update glfw to version with updated huntergate

Set default glfw version to 3.3.4-p1

Revert "Remove Android and iOS from build matrix"

This reverts commit be9c98c.

remove unnecessary version
@rbsheth rbsheth merged commit 4c59352 into cpp-pm:master Nov 15, 2021
@rbsheth
Copy link
Member

rbsheth commented Nov 15, 2021

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.

None yet

3 participants