autoconf
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: autoconf in pure MSVC environment?


From: Brandon J. Van Every
Subject: RE: autoconf in pure MSVC environment?
Date: Tue, 7 Sep 2004 13:56:28 -0700

Bruce Korb wrote:
> "Brandon J. Van Every" wrote:
>
> Please explain to me carefully why I should put a lot of effort into
> generating undocumented .sln files for a platform that I do not use,
> when there is nobody paying me to do so?

You shouldn't, as you don't care about the problem.  Some of us are more
cross-platform oriented than you are, so we should / do care.  For
instance, one of my strategic goals is to move the OCaml programmer
culture from UNIX-centric to platform neutral.  I can only do that by
getting tools to work equally well in both environments.

My point was simply that UNIXen aren't in a morally superior position as
far as cross-platform support.  They're just as disinterested in native
Windows support as Microsoft is in native UNIX support.

> It is true that "automake"
> is completely wound up in emitting code for "make", but where is there
> an engine for emitting ".sln" files that can be readily
> bolted to some-
> thing that emits Makefile.am's?  Am I hearing you volunteering?

I love it when open source guys throw the 'volunteering' word around.
It's very macho, like volunteerism is the only determinant of project
success.  We should all just run off to our cubicles by our lonesomes,
code up The Solution [TM], and inflict it upon the world like Zeus
inflicted Athena from his skull.

What I am doing at this time, is determining what piece of the puzzle is
Autoconf.  I am hoping someone around here *may* have crossed these
issues before, and *may* have already tried a few approaches.  In short,
I am doing my best to avoid Not Invented Here.  Or, someone *may* have
determined that said support is impossible, because of dependencies I'm
not aware of.

Open source communities seem to have 2 kinds of people in them:

- design first, code later
- code first, design later


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

"We live in a world of very bright people building
crappy software with total shit for tools and process."
                                - Ed Mckenzie





reply via email to

[Prev in Thread] Current Thread [Next in Thread]