Re: Is there a Windows version of SableVM?

--- Stephen Compall <[email protected]> wrote:

> Andy Madigan <[email protected]> writes:
> 
> > Also, wouldn't using the windows system directly mean big changes
> to
> > the code? That would seem to be a bad idea, unless building under
> > mingw lead to an unacceptably slow or big vm.
> 
> http://mingw.org/mingwfaq.shtml#faq-what
> 
>   MinGW uses the Microsoft runtime libraries, distributed with the
>   Windows operating system.
> 
> It's cygwin1.dll or changes.
> 
> Also, I believe fundamentally a MinGW build is no different than a
> Cygwin build with -mno-cygwin, and maybe -mms-bitfields.  So if a
> Cygwin environment is more comfortable, then it can be used for
> development and building without penalty.
> 
> Doesn't mean it's not going to be a pain to deal with.
> 
> --
> Stephen Compall or s11 or sirian
> 
> Unix will self-destruct in five seconds... 4... 3... 2... 1...
> 
> White Water terrorist LLNL lynch Comirex computer terrorism ASLET
> MP5K-SD USCOI Crowell FTS2000 Verisign Perl-RSA class struggle
> national information infrastructure
> 
> _______________________________________________
> SableVM-user mailing list
> [email protected]
> http://sablevm.org/lists/control/listinfo/sablevm-user
> 
The use of msvcr7.dll is different than using the dlls that come with
windows. I don't remember the exact language, but the GPL states that
GPL programs may link against core system libraries regardless of their
licensing terms (otherwise, no gnu app could have been used before they
had a free kernel). However, msvcr7.dll does not come with windows and
cannot be used with a GPL'd program. Also, even the cygwin dlls would
probably need to use windows functionality at some level. (note: this
probably doesn't apply to the lgpl)

I've also heard that --mno-cygwin may not work perfectly because the
mingw libs in cygwin don't include all the libs that come with mingw. I
would prefer to be able to use cygwin, getting a complex app like
SableVM to compile w/o bash and Unix-ish paths and libs would at the
very least require a new Makefile, at might even require compiling a
few other libs with MinGW just to get the right build deps.

--I used to be a DOS geek, now my most common error on windows is:
'ls' is not recognized as an internal or external command,
operable program or batch file.
(In other words: Get back to bash as fast as you can!)


=====