public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Eric McDonald <mcdonald@phy.cmich.edu>
To: "Brandon J. Van Every" <vanevery@indiegamedesign.com>
Cc: xconq <xconq7@sources.redhat.com>
Subject: Re: Standardizing the Windows build
Date: Sat, 08 Nov 2003 00:40:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0311071833300.10293-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <OOEALCJCKEBJBIJHCNJDAEFOGLAB.vanevery@indiegamedesign.com>

On Fri, 7 Nov 2003, Brandon J. Van Every wrote:

> >From private discussion with Eric, it seems there is no standard,
> canonical build environment for Xconq on Windows.  There aren't even any
> regular Windows developers, apparently?  Xconq development is
> Linux-centric 

I told you that Hans develops on the Mac.

> I am willing to do the work of creating MS Visual Studio project files,
> if we can come to a consensus on what the standards should be.  A
> non-exhaustive list of issues:
> 
> - TCL distributions.  Eric thinks the TCL binary currently distributed
> with Cygwin is broken.  I'm not sure myself, 

Actually, I'm the one who isn't sure. What I am pretty sure about 
is that the Cygwin Tcl installation on _your_ system is broken. If 
your TCL_INCLUDE_SPEC points to a nonexistent directory, then 
something isn't right. (And if this argument is going to reach 
flamewar crescendo again, let's take it back off-list.)

> - Religion about commercial IDEs.  If most of you think MS Visual Studio
> is Evil, then we aren't going to get anywhere.  Most of us Windoze

It's not a matter of being evil. I simply would not want to say 
that I would want that to be the only approved, supported way to 
build Xconq under Windows. I think it can and should be an 
alternative though. And if you make it a viable alternative, I 
can't imagine anyone complaining.

> I'd better give you full disclosure on my various development agendas.
> That way you can make up your mind whether I'd be a welcome contributor
> or a downright menace.

It's hard to be a menace to GPL'd code unless you're stealing 
copyrights or violating the rather liberal terms of the license.

> Second disclosure: I'm interested in DirectX and .NET stuff.  Sure it's

Some DirectX optimization for the Windows Tcl/Tk and SDL apps 
might be desirable.

Eric

  reply	other threads:[~2003-11-07 23:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-07 23:46 Brandon J. Van Every
2003-11-08  0:40 ` Eric McDonald [this message]
2003-11-08  1:29   ` Brandon J. Van Every
2003-11-08  1:34     ` Eric McDonald
2003-11-08  2:57       ` Brandon J. Van Every
2003-11-08  1:56 ` Hans Ronne
2003-11-08  2:33   ` Eric McDonald
2003-11-08  2:55     ` Hans Ronne
2003-11-08 11:38       ` Brandon J. Van Every
2003-11-08 22:27         ` Hans Ronne
2003-11-08 22:33           ` SDL and 3D Brandon J. Van Every
2003-11-08 23:29             ` Eric McDonald
2003-11-09  2:45             ` Hans Ronne
2003-11-09  3:33               ` whose Windoze build it is anyways Brandon J. Van Every
2003-11-09 12:52                 ` Stan Shebs
2003-11-08  3:06     ` Windows native UIs Brandon J. Van Every
2003-11-08 13:58       ` Hans Ronne
2003-11-08  3:10   ` The gory Xconq kernel Brandon J. Van Every
2003-11-08 13:06     ` Hans Ronne
2003-11-08 22:59       ` Ease of MSVC build Brandon J. Van Every
2003-11-09  0:28         ` Eric McDonald
2003-11-09  0:42           ` Brandon J. Van Every
2003-11-09  1:54             ` Brandon J. Van Every
2003-11-09  4:41       ` easy build trees for non-Xconq gurus Brandon J. Van Every

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=Pine.LNX.4.44.0311071833300.10293-100000@leon.phy.cmich.edu \
    --to=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).