public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: "Brandon J. Van Every" <vanevery@indiegamedesign.com>
To: "xconq" <xconq7@sources.redhat.com>
Subject: whose Windoze build it is anyways
Date: Sun, 09 Nov 2003 03:33:00 -0000	[thread overview]
Message-ID: <OOEALCJCKEBJBIJHCNJDCEGMGLAB.vanevery@indiegamedesign.com> (raw)
In-Reply-To: <l03130300bbd327610c54@[212.181.162.155]>

From: Hans Ronne [mailto:hronne@comhem.se]
>
> So far, all we have heard from you is that you are unable to
> build a simple
> Windows app, despite trying hard for a week. Which raises
> questions about
> your ability to contribute in a meaningful way to Xconq development.

Well equally, what you guys have proven is you don't competently
maintain and communicate a proper Windoze build enviornment.  Not can't,
but don't.  I'm sure you guys do fantastic Linux build maintenance.
Your treatment of Windoze leaves a lot to be desired.  Honestly, if you
pulled any of this stuff with your Linux build, people would laugh at
you.  They'd say you were bad Linux developers.  Since you're good Linux
and Mac developers, I don't exactly expect you to be good Windoze
developers.  But I do expect you to not make excuses for your worst
practices.

> To prove yourself, you would have to "shut up, buckle down,
> and do a little work" as Eric so aptly put it.

Tell you what.  You guys admit what you have put inadequate effort into
(where "inadequate" means by general standards of Windoze development,
not your personal needs), and I'll give you proper MSVC project files.
I'm not interested in hearing any more crap from you guys about how your
lousy Windoze build practices are somehow my fault.


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

20% of the world is real.
80% is gobbledygook we make up inside our own heads.

  reply	other threads:[~2003-11-09  2:45 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-07 23:46 Standardizing the Windows build Brandon J. Van Every
2003-11-08  0:40 ` Eric McDonald
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               ` Brandon J. Van Every [this message]
2003-11-09 12:52                 ` whose Windoze build it is anyways 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=OOEALCJCKEBJBIJHCNJDCEGMGLAB.vanevery@indiegamedesign.com \
    --to=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).