From: NiseVoid <NiseVoid@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Blender 3D - Wayland Support
Date: Thu, 05 Jan 2023 03:00:16 +0100 [thread overview]
Message-ID: <20230105020016.SJduUMlIxAEXLYbLSVfLyx-X_88WS_aCsxC3DloyUSI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38128@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 778 bytes --]
New comment by NiseVoid on void-packages repository
https://github.com/void-linux/void-packages/issues/38128#issuecomment-1371652655
Comment:
As far as I can tell blender 3.4 should have fixed the issue of not being able to support both X11 and wayland at the same time, and it looks like it released just under a month ago.
Setting the `WITH_GHOST_WAYLAND` flag on the build might be all that's needed, since I have locally built blender by modifying the template to add the wayland one and remove any conflicting flags (which were X11 and GLEW iirc). I also needed to add some wayland related depends and makedepends.
I am however not sure if there would be any other issues with updating blender. I assume that at the very least the paches would have to be updated.
next prev parent reply other threads:[~2023-01-05 2:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 13:11 [ISSUE] " jdnumm
2022-07-18 22:30 ` classabbyamp
2022-07-18 22:30 ` classabbyamp
2022-07-18 22:31 ` classabbyamp
2022-10-18 2:14 ` github-actions
2023-01-05 2:00 ` NiseVoid [this message]
2023-03-14 17:08 ` mhmdanas
2023-06-13 1:59 ` github-actions
2023-09-12 1:44 ` github-actions
2023-09-26 1:45 ` [ISSUE] [CLOSED] " github-actions
2024-01-07 15:04 ` Channpyae
2024-01-11 15:46 ` JetpackJackson
2024-01-11 16:54 ` Channpyae
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=20230105020016.SJduUMlIxAEXLYbLSVfLyx-X_88WS_aCsxC3DloyUSI@z \
--to=nisevoid@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).