From: "Robert Praetorius" <RPraetorius@AspenRes.Com>
To: cygwin@cygwin.com
Subject: Re: OT: MS Visual C++ Makefiles
Date: Fri, 08 Feb 2002 08:04:00 -0000 [thread overview]
Message-ID: <3C63B066.23578.289A0DEF@localhost> (raw)
In-Reply-To: <20020208125717.C12075@cygbert.vinschen.de>
> On Fri, Feb 08, 2002 at 11:21:55AM -0000, Simon McCaughey wrote:
> > Has anyone ever written a makefile converter so that a project written in MS
> > VC++ can be compiled with gcc?
> >
> > Would anyone else find this useful?
>
> This *might* be OT but actually I would find that useful, yes.
> I have no idea if sth. like that already exists.
I second this. Not from personal experience, but from having watched
a release engineers manually convert MSVC-generated makefiles into
something intelligible by humans, so that they could inject a bit of
flexibility and portability into the way things got built.
That is to say - I would not (yet) have had occasion to use it
myself, but I've certainly observed instances where it'd be useful.
And perhaps it'd make it easier for people who want to be less chained to
Microsoft and thereby encourage more open software development.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2002-02-08 16:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-08 3:19 Simon McCaughey
2002-02-08 3:57 ` Corinna Vinschen
2002-02-08 7:52 ` Christopher Faylor
2002-02-08 8:19 ` Norman Vine
2002-02-08 8:25 ` Tim Heath
2002-02-08 8:04 ` Robert Praetorius [this message]
2002-08-21 7:32 ` Soren A
2002-02-08 8:31 ` Daniel Adams
2002-02-08 19:01 ` Ryan T. Sammartino
2002-02-09 1:07 ` Simon McCaughey
2002-02-08 9:36 Ames Andreas (PN-SYS/A)
2002-08-23 13:33 John Vincent
2002-08-23 15:36 ` Gerrit P. Haase
2002-08-23 15:35 Polley Christopher W
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=3C63B066.23578.289A0DEF@localhost \
--to=rpraetorius@aspenres.com \
--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).