Sergey Khorev wrote:
I'd like to (excluding CMake stuff), but I'm very confused by your
words about lots of work :)
Support for Windows looks mature enough to not require daily hacking.
Can you please explain what are those big problems?
Also what will be modus operandi? E.g. shall maintainer just fish out
Windows-specific tasks from the maillist or you just have got lots of these?
_______________________________________________
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users
The Watcom compiler is probably moot to those not stuck with windows98.
However, it's advantages are worth considering: 1. works on all windows
2. has an IDE 3. simple install 4. mature but still being improved. The
Chicken header file needs to be modified where it says "ifdef _MSC_VER"
also check for "__WATCOMC__". Seems easy enough.
Windows C compilers are more alike than different so it is possible to
create an abstraction which works for them all. Since Chicken is a
program for writing programs, it could also output a Makefile for one's
favourite compiler. If Cmake already does that, and outputs a VC or
Borland
Makefile, then adding Watcom to the options won't be difficult.
IMO, maintaining a universal build tool that works for both windows and unix
is too complicated given the broken-minded idioms found on the windows
platform. Mingw and Cygwin only extend this complexity. So it is better
to have a separate windows build system.
regards,
-BobMc-
_______________________________________________
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users
