From: <sten.kristian.ivarsson@gmail.com>
To: <cygwin@cygwin.com>
Subject: Sv: Using cygwin-dll with msvc-exe
Date: Tue, 30 Jun 2020 09:15:33 +0200 [thread overview]
Message-ID: <000801d64eae$3ed3eb00$bc7bc100$@gmail.com> (raw)
In-Reply-To: <56b93fc2-1a64-4d53-5ce5-5038b263d251@SystematicSw.ab.ca>
[snip]
> They have incompatible internal startup and runtime environments including
> stuff like initialization, signal, and exit function handling
> (cygwin/newlib/gcc vs
> Windows/APIs/VC) although Cygwin can build Windows-loadable dlls and
> Windows-runnable exes and call Windows (system) dlls that don't depend on
> msvcrt.
What is interesting is that ldd on cygwin1.dll says it depends on
msvcrt.dll, but that might not be a problem ?
It seems like you could somehow fix it with this trick
https://cygwin.com/faq/faq.html#faq.programming.msvs-mingw (though I don't
really understand what difference it would make, because something seems to
be missing in the explanation (or more probably there's something I don't
understand;-) and it seems to be a bit cumbersome as well if you're having a
large product with a long lifetime)
In my honest opinion I think this disability to use cygwin-libraries from
windows-applications kind of limits some of cygwins purpose, but I do still
think cygwin is a great open source project ;-)
Best regards,
Kristian
next prev parent reply other threads:[~2020-06-30 7:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 9:31 sten.kristian.ivarsson
2020-06-26 17:13 ` Andrey Repin
2020-06-30 7:19 ` Sv: " sten.kristian.ivarsson
2020-06-26 17:32 ` Brian Inglis
2020-06-30 7:15 ` sten.kristian.ivarsson [this message]
2020-06-30 14:45 ` Brian Inglis
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='000801d64eae$3ed3eb00$bc7bc100$@gmail.com' \
--to=sten.kristian.ivarsson@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).