unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: John Kehayias <john.kehayias@protonmail.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: dan <i@dan.games>, guix-devel@gnu.org
Subject: Re: Should wsl-boot-program create XDG_RUNTIME_DIR?
Date: Wed, 16 Nov 2022 03:00:17 +0000	[thread overview]
Message-ID: <87sfijwqmb.fsf@protonmail.com> (raw)
In-Reply-To: <8735ajncp0.fsf@gmail.com>

Hi Maxim and Dan,

On Tue, Nov 15, 2022 at 04:13 PM, Maxim Cournoyer wrote:

> Hi Dan,
>
> dan <i@dan.games> writes:
>
>> 2. WSLg is usable, but the mesa in guix repo doesn't build with d3d12
>> gallium driver[2]. So when opening up a GUI software in guix on WSL,
>> in renders through llvmpipe (using CPU not GPU).
>>
>> I'm not sure if building mesa with d3d12 driver enabled by default is
>> a good idea, or maybe we could create a new package?
>
> A variant package would mean rebuilding many things, so if we want to
> support this use case it seems we'd have to enable d3d12 in our main
> mesa package and see what are the costs of doing so (increased disk
> space?  new dependencies?).

At the very least Mesa will need the DirectX headers. That may be it?

There are several Mesa updates over on core-updates, so if anyone wanted to try out adding that option, you should use the core-updates version. I think you'll only need the newer libdrm and wayland-protocols from there and should otherwise build fine on master.

John



  reply	other threads:[~2022-11-16  3:01 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 [this message]
2022-11-16  3:45     ` dan
2022-11-16  5:09       ` John Kehayias
  -- 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=87sfijwqmb.fsf@protonmail.com \
    --to=john.kehayias@protonmail.com \
    --cc=guix-devel@gnu.org \
    --cc=i@dan.games \
    --cc=maxim.cournoyer@gmail.com \
    /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).