From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-developers@cygwin.com
Subject: Re: Build spends a long time in "mkimport".
Date: Tue, 13 Oct 2020 12:30:09 +0200 [thread overview]
Message-ID: <20201013103009.GD26704@calimero.vinschen.de> (raw)
In-Reply-To: <19ee7db1-5f95-8ecc-4cdc-9c542cdb9e53@dronecode.org.uk>
On Oct 11 18:14, Jon Turney wrote:
> What I think mkimport is doing: This produces the import library for the
> Cygwin DLL, which is actually a 'hybrid' library. Mainly it consists of
> import stubs for functions in the DLL (some of which are renamed by
> --replace options), but it also contains some specific object files directly
> (this is stuff called by crt0.o, but idk why it's can't be in the DLL).
Some stuff must be statically linked into the executable to work.
For instance, see the stuff lib/_cygwin_crt0_common.cc sets up so
it will be available when calling into the DLL the first time.
Another heck of an example is lib/atexit.c with really detailed
comments in lib/atexit.c and dcrt0.cc.
Corinna
prev parent reply other threads:[~2020-10-13 10:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <af9f360a0a782f3c4db698e9f4584d16@mail.kylheku.com>
2020-10-11 7:24 ` Mark Geisert
2020-10-11 16:52 ` Ken Brown
2020-10-11 17:14 ` Jon Turney
2020-10-13 10:30 ` Corinna Vinschen [this message]
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=20201013103009.GD26704@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-developers@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).