public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Visual Studio linking
Date: Mon, 07 Jun 2004 14:56:00 -0000	[thread overview]
Message-ID: <20040607145637.GB15068@coe.casa.cgf.cx> (raw)
In-Reply-To: <Mahogany-0.66.0-604-20040607-153821.00@bakbone.co.uk>

On Mon, Jun 07, 2004 at 03:38:21PM +0100, Alastair Growcott wrote:
>Seriously, it is quite easy once you figure it out, and I am sure there
>are plenty of people who helped write Cygwin who probably knew but
>couldn't be bothered to tell me.

Well, we are all just very mean.

>It involves a couple of minor hacks.  It would be nice if cygwin1.dll
>could export the cygwin_crt0() function.
>
>Here is how you do it:
>
>1) Use the impdef program to generate a .def file for the cygwin1.dll
>impdef cygwin1.dll > cygwin1.def

A .def file is generated for cygwin when the DLL is built, actually.

>4) Use gcc in a Cygwin prompt to build my_crt0.c into a DLL (e.g.
>my_crt0.dll).  Follow steps 1 and 2 to generate .def and .lib files for
>the DLL.
>
>5) Download crt0.c from the cygwin website and include it in your
>sources.  Modify it to call my_crt0() instead of cygwin_crt0().

5a) Modify the license of your program to the GNU General Public
License, since your binary has now become GPLed, meaning that you must
now offer the source code to your sources under the terms of the GPL.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  reply	other threads:[~2004-06-07 14:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-02  8:20 Alastair Growcott
2004-06-02  8:52 ` Max Bowsher
2004-06-02  9:18   ` Re[2]: " Alastair Growcott
2004-06-02 12:16     ` Re[3]: " Alastair Growcott
2004-06-02 13:45       ` Re[4]: " Alastair Growcott
2004-06-02 13:55         ` Dave Korn
2004-06-07 14:40         ` Re[5]: " Alastair Growcott
2004-06-07 14:56           ` Christopher Faylor [this message]
2004-06-07 16:15             ` Re[2]: " Alastair Growcott
2004-06-07 16:25               ` Christopher Faylor
2004-06-08  9:04                 ` Alastair Growcott
2004-06-08 13:02                   ` Christopher Faylor
2004-06-07 20:42           ` Re[5]: " Joshua Daniel Franklin
2004-12-12 22:38 Daniel Starin
2004-12-12 22:55 ` Larry Hall
2004-12-17 21:35   ` Daniel Starin
2004-12-17 22:20     ` Larry Hall

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=20040607145637.GB15068@coe.casa.cgf.cx \
    --to=cgf-no-personal-reply-please@cygwin.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).