From: Hans Ronne <hronne@comhem.se>
To: Eric McDonald <mcdonald@phy.cmich.edu>
Cc: xconq7@sources.redhat.com, vanevery@indiegamedesign.com
Subject: Re: MSVC build environment?
Date: Mon, 03 Nov 2003 05:22:00 -0000 [thread overview]
Message-ID: <l03130300bbcb82314e78@[212.181.162.155]> (raw)
In-Reply-To: <Pine.LNX.4.44.0311022248270.2866-100000@leon.phy.cmich.edu>
>> > An alternative to cygwin/mingw is to use a Windows native build
>> > environment. It is now possible to build xconq for Windows
>> > using either Visual C or CodeWarrior.
>
>> as I can tell, and as far as you seem to say. So who is really doing
>> this?
>
>No one, afaik. I think Hans uses CodeWarrior.
Yep.
>> Is building under MSVC a reality, or a claim?
>
>It is not a claim. It _might_ be a reality. :-)
Juergen Ruehle posted instructions for how to build xconq under Visual C (I
think those were supposed to go into the empty part of INSTALL-win). I
tested it several months ago just to see if it worked, and it did.
Hans
next prev parent reply other threads:[~2003-11-03 4:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-03 1:38 Canonical Windows " Brandon J. Van Every
2003-11-03 2:00 ` Eric McDonald
2003-11-03 3:02 ` anonymous CVS missing Windows stuff? Brandon J. Van Every
2003-11-03 3:09 ` Brandon J. Van Every
2003-11-03 3:15 ` Hans Ronne
2003-11-03 3:36 ` Eric McDonald
2003-11-03 3:26 ` Eric McDonald
2003-11-03 2:43 ` Canonical Windows build environment? Hans Ronne
2003-11-03 3:52 ` MSVC " Brandon J. Van Every
2003-11-03 4:05 ` Eric McDonald
2003-11-03 5:22 ` Hans Ronne [this message]
2003-11-03 16:40 ` Juergen Ruehle
2003-11-03 11:20 ` Canonical Windows " Brandon J. Van Every
2003-11-03 15:02 ` Eric McDonald
2003-11-03 15:21 ` Juergen Ruehle
2003-11-03 15:52 ` Brandon J. Van Every
2003-11-03 16:57 ` Eric McDonald
2003-11-03 22:18 ` Brandon J. Van Every
2003-11-03 22:48 ` Eric McDonald
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='l03130300bbcb82314e78@[212.181.162.155]' \
--to=hronne@comhem.se \
--cc=mcdonald@phy.cmich.edu \
--cc=vanevery@indiegamedesign.com \
--cc=xconq7@sources.redhat.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).