DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=omBYtdKMgR0V1xtF
	blU2qocwUElCrjSuLAAAJfuRXUiUk5iIQSqQc0Ol1WBbSuM05Zh/JPQKjFYstl33
	GvlnqUBdo8wRbdjHkfTul+qqEmY7Cd4i2vtSbZ+Zu8qIayz5Yi4tzdjTZ+dR5sss
	MuOhT139hykkoFL6CzKrzzgxawg=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Reply-To: Brian DOT Inglis AT SystematicSw DOT ab DOT ca
Subject: Re: Is our use of Cygwin to build & run OpenOCD a good one?
To: cygwin AT cygwin DOT com
References: <ad7a93aa-d688-d177-bdf2-d368f2acbbd0 AT mindchasers DOT com>
From: Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Openpgp: preference=signencrypt
Message-ID: <b813b910-620e-8d26-f7a0-740c4aa94979@SystematicSw.ab.ca>
Date: Sun, 19 May 2019 15:21:46 -0600
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <ad7a93aa-d688-d177-bdf2-d368f2acbbd0@mindchasers.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

On 2019-05-19 13:43, Bob Cochran wrote:
> In case you're not familiar with it, OpenOCD is a hardware debugger that
> natively runs on Linux:  http://openocd.org/
> 
> We use it for embedded hardware development in debugging our ARM and FPGA code
> via JTAG (e.g., set breakpoints, step through code, etc.).   For our use, it
> interfaces to our hardware via an FTDI USB-based JTAG controller.
> 
> 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."

Probably from someone who tried Cygwin a decade ago and never since, or possibly
from someone who never tried it, or from MS.

> 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.

Ditto. If all you have access to is a Windows desktop, it's your only POSIX
compatible option. And as a distro Cygwin supports over 10k packages.
For interop from Windows to other boxes, Cygwin is a much lighter and more
integrated solution than a VM, and much more functional than WSL, as you can run
Unix daemons working as if Windows services, X and dependent window managers and
apps as on Unix, and develop and build them as well from their original source
code, using autotools or anything you'd use on another system.

> 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.

Great use case: don't let grumpy commentators drag you down.

-- 
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