From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Is our use of Cygwin to build & run OpenOCD a good one?
Date: Thu, 23 May 2019 01:47:00 -0000 [thread overview]
Message-ID: <3c3b3ab6-919b-8bc5-8467-4218b898d7bd@SystematicSw.ab.ca> (raw)
In-Reply-To: <548046265.20190523002828@yandex.ru>
On 2019-05-22 15:28, Andrey Repin wrote:
> Bob Cochran wrote:>> And I'm reluctant to install other translation projects on my PC like>> MSYS2
and MinGW because of bloat, support, and security concerns. Try >> to keep it as
simple as possible!> In case of Cygwin and MinGW, all you would be installing is
cross-compilers'> toolchain.> Then you run make from Cygwin, specifying correct
target, and get a native> Win32 executabe at the end.
First you have to check that you have all the library build dependencies you
need available in mingw64-x86_64-... packages, and install them (they install
into /usr/x86_64-w64-mingw32/sys-root/mingw/{lib,include} directories), and the
related mingw64-x86_64-binutils, which go in the same tree, then configure the
build to use those cross-tools, similar to how you would do an ARM cross-build
on x86 Linux.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-05-23 1:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-19 19:44 Bob Cochran
2019-05-19 20:53 ` LRN
2019-05-19 21:21 ` Brian Inglis
2019-05-20 14:16 ` Erik Soderquist
2019-05-20 14:27 ` Jose Isaias Cabrera
2019-05-20 18:49 ` Bob Cochran
2019-05-21 17:55 ` LRN
2019-05-21 18:21 ` Jose Isaias Cabrera
2019-05-22 6:05 ` Bob Cochran
2019-05-22 21:35 ` Andrey Repin
2019-05-23 1:47 ` Brian Inglis [this message]
2019-05-23 1:52 ` Brian Inglis
2019-05-23 1:55 ` Brian Inglis
2019-05-20 17:54 ` Achim Gratz
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=3c3b3ab6-919b-8bc5-8467-4218b898d7bd@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).