Github messages for voidlinux
 help / color / mirror / Atom feed
From: RoundDuckKira <RoundDuckKira@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: MangoHud: upload revision that depends on libXnvctrl to support Nvidia cards
Date: Tue, 23 May 2023 21:42:30 +0200	[thread overview]
Message-ID: <20230523194230.E1p1py8lE8U0sHiGIln0P9b_r0y4B8AK_I06GQUibRs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44051@inbox.vuxu.org>

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

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

MangoHud: upload revision that depends on libXnvctrl to support Nvidia cards
https://github.com/void-linux/void-packages/pull/44051

Description:
Set MangoHud to depend on libXnvctrl to fix Nvidia detection. This fixes a bug in the normal Void Linux package as is currently, where Nvidia GPUs aren't read at all, even if you force the Nvidia lspci number.  This is due to a lack of needed development files that libXnvctrl contains, so here I made this package dependent on that package and changed the settings to make it use the library in compilation.

That said this may mean the package may end up being x86_64 only as I didn't test a i386 version or other arches. Worst comes to worst, could it be possible then there would be a Nvidia version of this package?

EDIT: and oh yeah the CI will fail for this pull req as it requires #44050 to work.

<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**

<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->

#### Local build testing
- I built this PR locally for my native architecture, (x86_64)



      parent reply	other threads:[~2023-05-23 19:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-23 17:52 [PR PATCH] " RoundDuckKira
2023-05-23 18:15 ` Duncaen
2023-05-23 19:42 ` RoundDuckKira
2023-05-23 19:42 ` RoundDuckKira [this message]

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=20230523194230.E1p1py8lE8U0sHiGIln0P9b_r0y4B8AK_I06GQUibRs@z \
    --to=roundduckkira@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).