RE: Standardizing the Windows build

["Brandon J. Van Every" <vanevery at indiegamedesign dot com>]

From: Eric McDonald [mailto:mcdonald@phy.cmich.edu]
>
> > The policy should be, "We do this, we stress test it, and
> > we know that it works.
>
> If you wish to volunteer to be the person who upholds that policy,
> then please be my guest.

Let's find out if everyone / anyone else wants me to be "the guest."
While we're at it, let's find out if there are any Windoze developers
here?

> > 'Cept me.  Why should I support a Windoze build that nobody
> > else will stress test and develop with?
>
> I ask myself the same question.
>
> >I shouldn't.
>
> Then why should I? You seem to be complaining that we didn't do
> this for you, when you yourself wouldn't do it for others.

It's like this.  I'll build the standard environment if everyone agrees
to the standard, follows the standard, and the Windoze developers stress
test the standard.  (Are there any??)  I'm not going to do it if one
person says "I want it this way," another says "no, I want it that way!"
and nothing I build actually gets stress tested.  And finally, if I am
to take ownership of it, VS .NET 2003 has to be the primary build
environment.  Life is too short to screw around with all the other kinds
of pain.  There will have to be a Cygwin or MinGW custom build step, but
VS .NET 2003 is The Right Way Going Forwards to do mainstream Windoze
development.


Cheers,                     www.indiegamedesign.com
Brandon Van Every           Seattle, WA

Taking risk where others will not.