From: Eliot Moss <moss@cs.umass.edu>
To: Csaba Raduly <rcsaba@gmail.com>, Mike Gran <spk121@yahoo.com>
Cc: Cygwin List <cygwin@cygwin.com>
Subject: Re: Use cygwin to run autotools for MSVC?
Date: Thu, 26 Mar 2020 19:05:59 -0400 [thread overview]
Message-ID: <c82e3e8c-c79e-37c9-e56e-40b78355ceb9@cs.umass.edu> (raw)
In-Reply-To: <CAEhDDbDRF5C-feEhcbjBZWM2y6uX0TZzd=DcZs3yjnYV+JwpnQ@mail.gmail.com>
On 3/26/2020 5:37 PM, Csaba Raduly via Cygwin wrote:
> Hi Mike,
>
> On Thu, Mar 26, 2020 at 9:31 PM Mike Gran via Cygwin <cygwin@cygwin.com>
> wrote:
>
>> Hi-
>> Is it possible use Cygwin to run an autotools 'configure' script but have
>> the compiler be MSVC?
>>
>
> I would be very surprised if this worked. 'configure' is likely to run the
> compiler with unix-style flags (started with hyphens) rather than DOS-style
> flags (started with forward slashes). cl.exe may accept only DOS-style
> flags.
>
> Also, MSVC won't be able to find Cygwin's include files, and even if it
> did, most likely won't be able to compile them.
>
> The whole thing sounds like a recipe for failure. What are you trying to
> achieve?
All that said, I _have_ seen build processes organized to give MSVC
as an option ... and that in fact sometimes make it hard to do a Cygwin
build because they "want" to do a native Windows build!
However, this may have been more just a canned Makefile than a whole
./configure process ...
Eliot
next prev parent reply other threads:[~2020-03-26 23:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <537493096.2714240.1585254646086.ref@mail.yahoo.com>
2020-03-26 20:30 ` Mike Gran
2020-03-26 21:37 ` Csaba Raduly
2020-03-26 23:05 ` Eliot Moss [this message]
2020-03-27 12:48 ` Peter Dons Tychsen
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=c82e3e8c-c79e-37c9-e56e-40b78355ceb9@cs.umass.edu \
--to=moss@cs.umass.edu \
--cc=cygwin@cygwin.com \
--cc=rcsaba@gmail.com \
--cc=spk121@yahoo.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).