X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D50133857359 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1695381157; bh=jKRVeMA71VEtAymmrFnLKYk1m8CLKUiUKQvUA0Zrmk0=; h=Date:Subject:To:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=YxHjp/DdPs/mpmByPCNOdqmzBqRThAGnx5OIF7qQkL0u2XTX/bxOwYLy0iBhzsSJV ePROHQ3R5e5MECG6wULqrKFFq3ZQ0H4msVDe1eRwz9HGPetke4LukQlzRzh4By2yid 1rQsEaqAlZjYQfRpLsIubmexFp2Xg+W34psciY3k= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 504853858D28 Message-ID: Date: Fri, 22 Sep 2023 13:12:19 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:102.0) Gecko/20100101 Thunderbird/102.15.1 Subject: Re: Question on statically linking with cygwin To: cygwin AT cygwin DOT com References: In-Reply-To: X-Provags-ID: V03:K1:+abX9p4KsbPZbkpshadHGdVVyAhgyyIrMX/2RHKLwj63/+hAxsD laNm82imi2CZPa30+Cftt1hyvG9iESF8aUVNT9VLUTJMzSDzYd7lz7ttRI9Bn49dpPq+LkS RvTuuxRit42Kmj3g2YfjFlCFc2rDQfPS0Jdx7UU4Lyu9PAw0fLIgVh4lZURsROzhabS37OK NKkNlsXF6Ow0OFMYhZ0rQ== UI-OutboundReport: notjunk:1;M01:P0:MIWy3/NO9Ew=;uSZNbsWYHBLuNlqcBQovnli16Z3 Ljyu6a+przfitkCUjyZy5v1vPEqQZi0aBW+tnQNlE2JpyJb9WnLhk+FCHi3YNSRvXEESMNOH7 PpTZNHJxAz6CW5SmOxGPuBtkxSFpPdUU0Lh5ZTrFscJBk7COZ48FbB0asJ9jKOBkPyuXp221K jxjY+6HPRho2WXamlbDq4rpZgE6YxG9ijqzktR0/R0uNL91zjp1wOgbhXC15qHhgGILrVa/Rm C92/H14zw8EfU9S1ug2npzzDY56uAVPaLYaPY0OnlWO36QU3qK1DIEq38M+zGxop8ZCQK0KDc nOTPRX82jrn656HFc9ia6vxJmvgOYCaRoYOqEthHXwX0DpZ2EpHNiUi9X0dbF1coFlgjjGYPz x3E/5jRi+TtAN95CvT/ls658kckxAOS1e3XkIezGRLXp+gRI7bfmgLQFFZ/cP/H+fDnXJug/O 0A4hEUP0CTDLDyVUnEsrhZ9zMxjHFmgHKiAIxsbkBVR+H8nWT1oevNM3z7e7hVbnSftuqeqWg m6ccvfhFghUB5uZ0GTFF2feCO+fKF+4WBYzMiJfT3g6QNapqtbk+3pnsNb0fCRDyhbgy+TVSc +hi2qzLpcObgC4hG9aXT/4juk6ib4HmjXIMS6+T7VhUA3IThwkJxIIXHBKaTZe2EYxqdMkwua HACT9OPzL9RG9i8MqS/5N4K/T4P3qYGDXcxYKdUePWn2YxkQwMCH4JC+ifb4y9L/5g7cSOgPn I94mQF6tkswVBz/gAO8Zr/Fe25aIX91ETzVl7+USuOr9h1L0T7+0dl3GiDQexJoNZaNSVkkTq TOpjWyaNDZQebr0d9dLtu1MOFLo3Z8qOFRUwM3h6Yl4IAJbltceJ/2ueABA5uvyZbHGnXZcit v9ZV5Vt8FZW+gdg== X-Spam-Status: No, score=-2.4 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H5, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.30 List-Id: General Cygwin discussions and problem reports List-Archive: List-Post: List-Help: List-Subscribe: , From: Johannes Thoma via Cygwin Reply-To: Johannes Thoma Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: "Cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 38MBCdGY002745 Hi Martin, Thanks for your answer, comments inline: Am 22.09.23 um 07:54 schrieb Martin Wege via Cygwin: > On Tue, Sep 19, 2023 at 5:24 PM Johannes Thoma via Cygwin > 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? I read that in the Cygwin FAQ: https://cygwin.com/faq/faq.html#faq.programming.static-linking I read through the licensing options and IMHO linking statically against cygwin (which is GPL) from a program (like WinDRBD) that is also GPL should be allowed. But I am not a lawyer ... > >> 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? > I would build my own cygwin1.lib or cygwin1.a and statically link against it. > Thanks, > Martin > Best regards, - Johannes -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple