From: Filipp Andjelo <filipp.andjelo@tomtom.com>
To: <crossgcc@sourceware.org>
Subject: Build x86_64-w64-mingw with dynamic libraries
Date: Mon, 12 Dec 2016 15:17:00 -0000 [thread overview]
Message-ID: <836a1c02-50a3-292c-e761-00e746fa9cf3@tomtom.com> (raw)
Hi guys,
when building cross x86_64-w64-mingw using crosstool-ng, I'm always
getting only static target libraries (libc, stdc++ s.o.), where I'd like
to have them shared (dynamic DLLs). I setup to build host static cross
toolchain to make it relocatable on linux, however I'd like to have
shared output for the target (windows). I managed to build the toolchain
with static and dynamic libraries outside of ct-ng, however I'm using
multiple targets and all of them have being created useing ct-ng and I'd
like not to break this rule. I hope, you understand my problem and can
tell how to convince ct-ng to build with DLLs.
Thanks in advance,
Filipp
--
Filipp Andjelo | Sr Software Engineer | Product Unit NDS |
filipp.andjelo@tomtom.com | +49 (0) 5127 408395 | www.tomtom.com
reply other threads:[~2016-12-12 15:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=836a1c02-50a3-292c-e761-00e746fa9cf3@tomtom.com \
--to=filipp.andjelo@tomtom.com \
--cc=crossgcc@sourceware.org \
/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).