public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Martin Wege <martin.l.wege@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Question on statically linking with cygwin
Date: Fri, 22 Sep 2023 07:54:12 +0200	[thread overview]
Message-ID: <CANH4o6NP+ag1HNPPoqkWAZw0KK2Fnc22_4vt1m2QgByhr5Pb0w@mail.gmail.com> (raw)
In-Reply-To: <b6d9c9d9-63ae-7238-cd77-6f3de051eb5d@gmx.at>

On Tue, Sep 19, 2023 at 5:24 PM Johannes Thoma via Cygwin
<cygwin@cygwin.com> wrote:
>
> Hi,
>
> As I understood the reason for not being able to statically link
> the cygwin1.dll in to a binary and distribute that is because of
> licensing issues.

Do you have any references for that?

> Are there any technical issues that would make
> it impossible to link with cygwin statically?
>
> The reason I am asking is I am working on a GPL project
> (WinDRBD: https://github.com/LINBIT/windrbd) and am currently
> delivering the cygwin1.dll along with the binary. It would be
> desireable to have the cygwin1.dll statically linked (for example
> to avoid version clashes) instead. Is that technically possible?
> If necessary I am ready to compile cygwin (at least the needed
> files) on my own.

Interesting.
But how (from a developers perspective) do you link cygwin1.dll
statically into a binary?

Thanks,
Martin

  reply	other threads:[~2023-09-22  5:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-19 15:24 Johannes Thoma
2023-09-22  5:54 ` Martin Wege [this message]
2023-09-22 11:12   ` Johannes Thoma
2023-10-16 15:28     ` Jon Turney
2023-11-02 17:33       ` Johannes Thoma
2023-11-03 15:48         ` Johannes Thoma

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=CANH4o6NP+ag1HNPPoqkWAZw0KK2Fnc22_4vt1m2QgByhr5Pb0w@mail.gmail.com \
    --to=martin.l.wege@gmail.com \
    --cc=cygwin@cygwin.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.
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).