From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: External static library within Cygwin
Date: Mon, 22 Mar 2021 18:15:44 +0100 [thread overview]
Message-ID: <e79ae96a-a87b-6aa9-36bc-aff1462549d1@gmail.com> (raw)
In-Reply-To: <CADn5QPys9B2+xWSPQXOKD7e6jenc0Zu71ewKo8or2T5NqBEU3w@mail.gmail.com>
On 22.03.2021 15:43, Jeff Josephs wrote:
> I have a third party external static library in native Windows, and I am
> trying to use it within my Cygwin project. After looking at the static
> library, I noticed that it uses name mangling, and when compiling the
> Cygwin project, I get undefined references.
>
> Aside from modifying the third party library to not do the name mangling,
> is there anything within Cygwin that I can do to solve the undefined
> references with the name mangled functions?
mangling is typical of C++ and different compilers have different
ways.
About mixing Native Windows, please note the difference
between LLP64 and LP64
https://cygwin.com/cygwin-ug-net/programming.html
prev parent reply other threads:[~2021-03-22 17:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 14:43 Jeff Josephs
2021-03-22 17:15 ` Marco Atzeri [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=e79ae96a-a87b-6aa9-36bc-aff1462549d1@gmail.com \
--to=marco.atzeri@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).