From: Eliot Moss <moss@cs.umass.edu>
To: Ken Brown <kbrown@cornell.edu>,
Johnathan Schneider <johnny.schneider10@outlook.com>,
"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Workaround for cygwin's way of linking folders?
Date: Sun, 6 Dec 2020 20:39:04 -0500 [thread overview]
Message-ID: <c02dcb60-5327-86f3-e704-839af7ca63b3@cs.umass.edu> (raw)
In-Reply-To: <b0bd9dcf-15cc-8c01-ea9d-17562d14ab1d@cornell.edu>
On 12/6/2020 6:45 PM, Ken Brown via Cygwin wrote:
> On 12/6/2020 5:41 PM, Johnathan Schneider via Cygwin wrote:
>> Hi all,
>>
>> I'm setting up a cross platform development environment using Cygwin. Upon attempting to use
>> Cygwin's CMake that is natively bundled, I discovered that Cygwin goes looking for the gcc in
>> /usr/bin/cc, a folder that does not exist according to windows. I have familiarized myself with
>> the Cygwin way of organizing it's folders, seen here
>> https://cygwin.com/faq.html#faq.using.shortcuts and
>> https://cygwin.com/faq.html#faq.using.directory-structure and thus I know that Cygwin's /usr/bin
>> folder is in fact /bin - according to windows, anyways. However, I'm not familiar with how to work
>> around that on windows. In particular, virtually all of my IDEs' attempts to call CMake fail,
>> because I proceed to ask it to call the gcc and windows, as is explained in the above FAQ's, does
>> not recognize the Cygwin-way of referencing folders.
>>
>> Alas, my question - what is the recommended workaround?
>
> It's hard to answer this question without knowing exactly what your IDE is doing. Can you give a
> detailed recipe for reproducing the problem without using an IDE? In general, Cygwin's CMake should
> have no problem executing /usr/bin/cc unless something is interfering with Cygwin's normal path
> handling routines.
My guess: Your IDE is Windows based, and it is unlikely to play well with Cygwin. It probably
expects Windows paths, etc. MinGW might gives Unix-like tools that work better for you, or you can
find Windows based CMake, C compilers, etc.
With some effort, you _might_ get the IDEA to invoke the Cygwin program by giving the full Windows
path to it, but /usr/bin/cc is going to expect Cygwin format paths, which a Windows based IDE won't
know anything about ...
My guess could be wrong, of course!
Regards - Eliot Moss
next prev parent reply other threads:[~2020-12-07 1:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-06 22:41 Johnathan Schneider
2020-12-06 23:45 ` Ken Brown
2020-12-07 1:39 ` Eliot Moss [this message]
2020-12-07 7:27 ` L A Walsh
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=c02dcb60-5327-86f3-e704-839af7ca63b3@cs.umass.edu \
--to=moss@cs.umass.edu \
--cc=cygwin@cygwin.com \
--cc=johnny.schneider10@outlook.com \
--cc=kbrown@cornell.edu \
/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).