From: "Ludovic Courtès" <ludo@gnu.org>
To: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
Cc: Vivien Kraus <vivien@planete-kraus.eu>, 56504@debbugs.gnu.org
Subject: [bug#56504] [PATCH] Mingw support for zlib
Date: Tue, 19 Jul 2022 23:07:27 +0200 [thread overview]
Message-ID: <871qugreuo.fsf_-_@gnu.org> (raw)
In-Reply-To: <973e2566abcd13f7612f1d69a59188220b67b337.camel@ist.tugraz.at> (Liliana Marie Prikler's message of "Fri, 15 Jul 2022 16:30:59 +0200")
Hey Liliana,
Liliana Marie Prikler <liliana.prikler@ist.tugraz.at> skribis:
> Am Freitag, dem 15.07.2022 um 16:28 +0200 schrieb Vivien Kraus:
>> Le jeudi 14 juillet 2022 à 08:01 +0200, Liliana Marie Prikler a
>> écrit :
>> > > > 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?
>> I’m not sure I understand. I think that’s what I did, and obviously
>> it
>> works since the dll is installed in the default output. Could you
>> explain a bit more the phrase "we could set it"?
>>
>> Vivien
> My bad; I didn't notice the attachments. LGTM
Please do apply what LGTY, thanks!
Ludo’.
next prev parent reply other threads:[~2022-07-19 21:08 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
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 [this message]
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
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=871qugreuo.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=56504@debbugs.gnu.org \
--cc=liliana.prikler@ist.tugraz.at \
--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 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).