CMake is not finding a usable cc on my cygwin system, I've tried many things.

[David Dyck]

I had to get around cygwin and cmake when working with external (
non-cygwin ) cross compilers for the arm.
I found I needed to to some tricks with mount and symbolic links so  I
could avoid c:/ paths
I observed that msys type tools would accept /c/ paths and have had success
with the pico-sdk and it's cmake cygwin

On Sat, Jul 19, 2025 at 9:13 PM Duncan Roe via Cygwin <cygwin@cygwin.com>
wrote:

> Hi Jon,
>
> On Sat, Jul 19, 2025 at 01:45:18PM -0400, cygwin wrote:
> > I just worked the CMake configuration command
> >
> >    cmake -G"Unix Makefiles"
> > /cygdrive/C/Users/somia/Downloads/libjpeg-turbo-3.1.1/
> >
> > and my woes were definitely due to having an msys cmake in my PATH. So,
> > guys, the guesses that I was trying with a Windows CMake were close but
> not
> > right on. It was *bash* that was my downfall, oddly enough. The first
> time
> > I invoked cmake I didn't have a cygwin cmake, and bash found the command
> > late in my PATH in the MSYS tree and hashed (stored) that path, so that
> > even after I installed cygwin cmake it kept calling msys cmake. Msys
> cmake
> > has now gone away for a lengthy vacation and cygwin cmake is producing a
> > configuration that is not quite successful but at least is more complete,
> > with real configure errors.
> >
> Bash's `type` builtin would have told you that. `type` also tells you about
> aliases and functions, unlike `which` which I haven't used for ages.
>
> Cheers ... Duncan.
>
> --
> Problem reports:      https://cygwin.com/problems.html
> FAQ:                  https://cygwin.com/faq/
> Documentation:        https://cygwin.com/docs.html
> Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple
>