The interpreter on Windows no longer builds under Visual C++ 6.0. That is probably fixable, but before much time is spent on it we should discuss the minimum compiler version we intend to support.
Obviously to build the 64-bit version we'll need a later compiler than Visual C++ 6.0. But for the 32-bit build we could maybe still support 6.0. Should we? Is it worth it? What compiler version is on the build machine? What version of the compiler should we build the release package with? I forget what the official name of Visual C++ 7 is, if it's .Net or 2003. I've got a copy of each compiler since 6.0, so I can build the official release with whatever we decide to use, so that's not a problem. I'd just as soon build the official release with Visual Studio 2005. But, we might have problems with people building their own external functions and linking with the interpreter. Problems with the C run time libraries. To tell the truth, I'm not real knowledgeable in that area. It seems to me, we should have problems, but the couple of quick tests I've done over the last year didn't show any problems. -- Mark Miesfeld ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
