Github messages for voidlinux
 help / color / mirror / Atom feed
From: CaitCatDev <CaitCatDev@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: Update libdecor to 0.2.2 and gamescope to 3.14.23
Date: Fri, 19 Jul 2024 18:40:10 +0200	[thread overview]
Message-ID: <20240719164010.ED89C220CF@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-51338@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 2144 bytes --]

There's a closed pull request on the void-packages repository

Update libdecor to 0.2.2 and gamescope to 3.14.23
https://github.com/void-linux/void-packages/pull/51338

Description:
## Update Gamescope and libdecor
I've updated gamescope and libdecor(as new gamescope needs it). This is because I was having issues with the version packaged with Void being the camera in games spinning uncontrollably.

Notes about this update in this time Gamescope has moved to using tagged versions of wlroots and libliftoff so for that purpose I've changed the gamescope build template to pull in the commits that gamescope is looking for and updated the dependencies of gamescope(removed wlroots and libliftoff as they are now built in) and added things such as libinput which used to be pulled in by wlroots.

The disabling "Werror" on libliftoff and wlroots was needed as both of them make use of code that can produce warnings based on compiler version. and the version of GCC shipped in void triggers those warnings. However these warnings are due to unused variables and not anything that is likely to cause major issue.

Please let me know if these would be accepted as is or if you would require me to make any adjustments.

### Summary of changes
libdecor 0.1.1 -> 0.2.2
gamescope 3.14.2 -> 3.14.23

#### Testing the changes
- I tested the changes in this PR: Briefly(Would love to get more people to test on more games)
I attempted to get 3.14.24 to work however was experiencing crashing issues to do with the pointer leaving the gamescope window/surface. So feel back to 3.14.23 (I've tested on the games I have access to Warcraft 3, WoW, Command and Conquer 95-Tib sun)

I've also tested some SDL2 and steam games as I am aware that steam and SDL2 both also pull in libdecor and they also seemed to work fine.

#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
- I've not tested on any other arch's as I do not have access to hardware.

ps. this is my first time packaging anything please let me know if I've made a mistake or misunderstood the system :3



Thanks 
- Cat

  parent reply	other threads:[~2024-07-19 16:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-19 15:14 [PR PATCH] updated libdecor and gamescope CaitCatDev
2024-07-19 15:27 ` Update libdecor to 0.2.2 and gamescope to 3.14.23 CaitCatDev
2024-07-19 16:10 ` abenson
2024-07-19 16:40 ` CaitCatDev [this message]
2024-07-19 16:54 ` CaitCatDev
2024-07-19 16:57 ` CaitCatDev
2024-07-19 17:52 ` dexgs
2024-07-19 16:53 [PR PATCH] Update Gamescope and libdecor CaitCatDev
2024-07-19 18:28 ` [PR PATCH] [Closed]: Update libdecor to 0.2.2 and gamescope to 3.14.23 CaitCatDev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240719164010.ED89C220CF@inbox.vuxu.org \
    --to=caitcatdev@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).