From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Is our use of Cygwin to build & run OpenOCD a good one?
Date: Mon, 20 May 2019 17:54:00 -0000 [thread overview]
Message-ID: <87k1elui4o.fsf@Rainer.invalid> (raw)
In-Reply-To: <ad7a93aa-d688-d177-bdf2-d368f2acbbd0@mindchasers.com> (Bob Cochran's message of "Sun, 19 May 2019 15:43:56 -0400")
Bob Cochran writes:
> We recently wrote up our process on building OpenOCD using Cygwin on
> Windows 10 and shared it on the OpenOCD mail list. And, I received
> the following feedback:
>
> "Cygwin? this is probably still functional, but now can be considered
> a (pre)historic solution."
More likely a fossilized memory of a very old Cygwin by that commenter.
> I personally have been using Cygwin for many years and have come to
> trust it for interfacing to Linux and macOS boxes from Windows. I
> think it's a great project, so when I wanted to build & run OpenOCD
> from scratch, I naturally went to Cygwin.
>
> I would appreciate any feedback on our use of Cygwin for building &
> running OpenOCD: https://mindchasers.com/dev/openocd-darsena-windows
>
> If fellow Cygwin users think it's a poor use case, then we'll pull the
> article.
It works, you don't have to jump through burning hoops to get there and
it helps you out for when you have to use a Windows box. So, all around
a good use-case, really.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf Blofeld V1.15B11:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
--
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
prev parent reply other threads:[~2019-05-20 17:54 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
2019-05-23 1:52 ` Brian Inglis
2019-05-23 1:55 ` Brian Inglis
2019-05-20 17:54 ` Achim Gratz [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=87k1elui4o.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).