unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: John Kehayias <john.kehayias@protonmail.com>
To: dan <i@dan.games>
Cc: guix-devel@gnu.org
Subject: Re: Should wsl-boot-program create XDG_RUNTIME_DIR?
Date: Wed, 16 Nov 2022 05:09:36 +0000	[thread overview]
Message-ID: <87r0y3wkms.fsf@protonmail.com> (raw)
In-Reply-To: <29840e81-c6b6-8518-edd5-5f20a5af732e@dan.games>

Hi Dan,

On Wed, Nov 16, 2022 at 11:45 AM, dan wrote:

> Hi John,
>
> On 11/16/2022 11:00 AM, John Kehayias wrote:
>> At the very least Mesa will need the DirectX headers. That may be it?
>
> According to the document of mesa[1], I believe it's doing more than
> just including headers:
>> The D3D12 driver is a Gallium driver that emits API calls for Microsoft’s D3D12 API
>> instead of targeting a specific GPU architecture.

Right, but that might just need the headers to know the API calls to make. My quick look at the build option discussions only referenced needing the headers. I would start there and see how far it gets :)

> Anyway, I could take the effort into investigating if it's gonna work on
> WSL if we add d3d12 support to the gallium3d driver, but I'm afraid I
> don't have the ability to test if it breaks anything on other platform /
> for other use cases.
>

Well Mesa updates go on core-updates anyway, so there is time (to test). I saw that Arch, for instance, enables this option in their regular Mesa build, for what that's worth.

Good luck!

> [1]: <https://docs.mesa3d.org/drivers/d3d12.html>



  reply	other threads:[~2022-11-16  5:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07  6:00 Should wsl-boot-program create XDG_RUNTIME_DIR? dan
2022-11-15 21:13 ` Maxim Cournoyer
2022-11-16  3:00   ` John Kehayias
2022-11-16  3:45     ` dan
2022-11-16  5:09       ` John Kehayias [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-11-07  6:06 dan
2022-11-07  6:09 dan

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87r0y3wkms.fsf@protonmail.com \
    --to=john.kehayias@protonmail.com \
    --cc=guix-devel@gnu.org \
    --cc=i@dan.games \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).