From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Mark H Weaver <mhw@netris.org>, zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: emacs-lucid (was Re: Emacs closure at ~900MB?)
Date: Tue, 29 Sep 2020 09:56:25 +0200 [thread overview]
Message-ID: <87h7rhrp7a.fsf@ambrevar.xyz> (raw)
In-Reply-To: <87r1qlhe1s.fsf@netris.org>
[-- Attachment #1: Type: text/plain, Size: 1353 bytes --]
Mark H Weaver <mhw@netris.org> writes:
> LLVM is an optional input for Mesa which enables the Gallium 'llvmpipe'
> driver, a fast software rasterizer that uses LLVM to do runtime code
> generation.
>
> https://docs.mesa3d.org/gallium/drivers/llvmpipe.html
>
> Among other things, this allows use of the GNOME Shell on systems
> without hardware support for 3D graphics.
>
> GTK depends on Mesa.
>
> ...
>
> Alternatively, for those who do not wish to maintain their own private
> branch, here's a hybrid approach that might be workable: add a local
> variant of 'mesa' with 'llvm' removed from 'inputs' (and "-Dllvm=true"
> removed from the configure flags), then add a local variant of 'gtk+'
> that uses your local 'mesa', and finally add a local variant of 'emacs'
> that uses your local 'gtk+'. I guess those last two steps could be
> replaced by deep package rewrites, although I've never used that
> functionality since I prefer the more flexible "private git branch"
> approach to customizing Guix to my preferences.
If I understand correctly, we could have a gtk-minimal that depends on
mesa-minimal which is built without LLVM. If llvmpipe is only useful
for GNOME Shell and the like, it's very likely that Emacs and many other
packages don't need GTK-on-LLVM.
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]
next prev parent reply other threads:[~2020-09-29 8:03 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 11:16 Emacs closure at ~900MB? zimoun
2020-09-22 11:31 ` Pierre Neidhardt
2020-09-22 11:34 ` zimoun
2020-09-22 11:45 ` Pierre Neidhardt
2020-09-22 11:50 ` Efraim Flashner
2020-09-24 17:28 ` emacs-lucid (was Re: Emacs closure at ~900MB?) Giovanni Biscuolo
2020-09-24 18:08 ` zimoun
2020-09-25 8:28 ` Giovanni Biscuolo
2020-09-25 10:23 ` Pierre Neidhardt
2020-09-25 23:06 ` zimoun
2020-09-29 8:42 ` Giovanni Biscuolo
2020-09-29 9:51 ` zimoun
2020-09-29 10:44 ` Giovanni Biscuolo
2020-09-26 16:32 ` Mark H Weaver
2020-09-26 18:26 ` Pierre Neidhardt
2020-09-26 21:26 ` Mark H Weaver
2020-09-27 6:33 ` Pierre Neidhardt
2020-09-27 10:53 ` Pierre Neidhardt
2020-09-27 20:49 ` Bonface M. K.
2020-09-28 6:43 ` Pierre Neidhardt
2020-09-28 10:49 ` Bonface M. K.
2020-09-28 8:56 ` zimoun
2020-09-28 9:25 ` Pierre Neidhardt
2020-09-28 12:02 ` zimoun
2020-09-28 14:42 ` Pierre Neidhardt
2020-09-28 19:16 ` Bengt Richter
2020-09-28 19:21 ` zimoun
2020-09-28 8:40 ` zimoun
2020-09-28 9:25 ` Pierre Neidhardt
2020-09-28 19:54 ` Mark H Weaver
2020-09-29 7:56 ` Pierre Neidhardt [this message]
2020-09-29 8:49 ` Giovanni Biscuolo
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=87h7rhrp7a.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.org \
--cc=zimon.toutoune@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).