From: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
To: Vivien Kraus <vivien@planete-kraus.eu>, 56504@debbugs.gnu.org
Subject: [bug#56504] [PATCH] Mingw support for zlib
Date: Thu, 14 Jul 2022 08:01:41 +0200 [thread overview]
Message-ID: <b97100e6044e6cb20f35130d799c157dd68b36a1.camel@ist.tugraz.at> (raw)
In-Reply-To: <d9ac8a144f4a442d4f9d0d6d996dd8962b0c3a8a.camel@planete-kraus.eu>
Am Mittwoch, dem 13.07.2022 um 17:19 +0200 schrieb Vivien Kraus:
> [...]
> Looking at the "-builder" scheme file that is generated for the
> derivation, it looks like what I want is simply %outputs, not %build-
> outputs.
Yeah, my bad, it's %build-inputs and %outputs respectively.
>
> > Oh, so you mean the static output should be built without
> > SHARED_MODE?
> No, SHARED_MODE=1 means "please also install the DLL" and
> SHARED_MODE=0 means "please do not install the DLL". Reading the
> win32/Makefile.gcc, nothing special is done if SHARED_MODE=0.
In that case we could set it via #:make-flags, right?
> It is only used in the install and uninstall targets. I don’t really
> understand why you would want to set SHARED_MODE=0 (even weirder to
> set it as a default) but I guess it happens.
Perhaps the rationale is that users might not actually want the shared
libraries for some bespoke reasons (not that those reasons would apply
to Guix users).
Cheers
next prev parent reply other threads:[~2022-07-14 6:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 23:53 [bug#56504] [PATCH] Mingw support for zlib Vivien Kraus via Guix-patches via
2022-07-12 6:07 ` Liliana Marie Prikler
2022-07-12 16:45 ` Vivien Kraus via Guix-patches via
2022-07-13 5:49 ` Liliana Marie Prikler
2022-07-13 15:19 ` Vivien Kraus via Guix-patches via
2022-07-14 6:01 ` Liliana Marie Prikler [this message]
2022-07-15 14:28 ` Vivien Kraus via Guix-patches via
2022-07-15 14:30 ` Liliana Marie Prikler
2022-07-19 21:07 ` Ludovic Courtès
2022-07-31 11:21 ` bug#56504: " Liliana Marie Prikler
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=b97100e6044e6cb20f35130d799c157dd68b36a1.camel@ist.tugraz.at \
--to=liliana.prikler@ist.tugraz.at \
--cc=56504@debbugs.gnu.org \
--cc=vivien@planete-kraus.eu \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.