[M3devel] CM3 on Win32 (MinGW)

[Jay]

(ps: more complete list:
 
 
NT386GNU:
 gcc backend 
 gcc for C compiler
 gcc/GNU ld for linker
 cygwin C runtime 
 X windows
 pthreads
 forward slashes on paths
 debuggable with gdb ("stabs" debug format) 
   or printf.. 
 
 
NT386MINGNU
 gcc backend  
 gcc for C compiler 
 gcc/GNU ld for linker 
 MS C runtime (provided by mingw's gcc) 
 I think debuggable with gdb. ("stabs" debug format) 
   or printf.. 
 Win32 windows 
 Win32 threads 
 backwards slashes on paths, or forward
 
 
NT386:
  integrated backend -- very fast 
  no 64 bit LONGINT 
  Visual C++ compiler/linker/runtime 
  Win32 thread/windows 
  backwards slashes on paths, or forward 
  debugable with Visual Studio/cdb/ntsd/windbg ("CodeView" debug format), not gdb 
   or printf.. 
)
 
 
The various factors are mixable/matchable to SOME extent, but they aren't tested, they might be confusing, and they don't all work necessarily.
These are "friendly" names to encompass a set of underlying factors.
I think I386_NT or I386_MSWIN, I386_CYGWIN, I386_MINGWIN might be better names.
(I would avoid saying "WIN32" anywhere, due to Windows also running on IA64 and AMD64).
 
 
 - Jay



----------------------------------------
> From: jay.krell at cornell.edu
> To: wagner at elegosoft.com; rv82 at ya.ru
> Date: Tue, 17 Feb 2009 07:20:13 +0000
> CC: m3devel at elegosoft.com; m3-support at elego.de
> Subject: Re: [M3devel] CM3 on Win32 (MinGW)
>
>
> NT386GNU corresponds to cygwin.
> It uses the gcc backend (has a 64 bit integer), and Cygwin runtime, pthreads, and forward slashes on all paths.
>
>
> NT386MINGNU corresponds to mingwin.
> It uses the gcc backend (has a 64 bit integer), MS runtime, Win32 threads, backwards slashes on all paths, but is ok with forward slashes, but doesn't do any "fancy" path conversions -- c:/windows is ok for example.
>
>
> NT386MINGNU was working, at least for command line apps.
>
> I can spin another build, make sure it still works, and maybe get around to fixing gui apps.
> (I think I'll just put in a small workaround for the gui issue.)
>
>
> In the meantime, can try cygwin?
>
>
> Anyone ok if I rename these I386_CYGWIN and I386_MINGW or I386_MINGWIN?
>
>
> - Jay
>
>
>
> ----------------------------------------
>> Date: Tue, 17 Feb 2009 08:01:35 +0100
>> From: wagner at elegosoft.com
>> To: rv82 at ya.ru
>> CC: m3devel at elegosoft.com; m3-support at elego.de
>> Subject: Re: [M3devel] CM3 on Win32 (MinGW)
>>
>> Quoting Воронов Роман :
>>
>>> Hello! At first, excuse me, but my english is very-very bad!
>>>
>>> 1. I try to build CM3 on Windows XP with MinGW toolset. But when I
>>> build m3core and libm3, there are many errors appears. I use
>>> cm3-min-WIN32-NT386GNU-d5.5.1 and
>>> cm3-src-all-d5.7.1-2009-02-09-15-06-52.tgz. May you recomend me, how
>>> to build m3core and libm3? All other libraries and packages I'll
>>> build manually.
>>
>> This may be best answered on the m3devel list, but you'll probably have
>> to provide some more details as to the many errors.
>> There should be a binary installation archive for CM3 based on
>> Cygwin in the upload area of www.opencm3.net.
>>
>>> 2. Tell me please, may I put binary package of CM3 for Win32 on my
>>> own site for public downloads?
>>
>> That should be no problem. You can also upload new packages you
>> want to publish to www.opencm3.net.
>>
>> Olaf
>> --
>> Olaf Wagner -- elego Software Solutions GmbH
>> Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
>> phone: +49 30 23 45 86 96 mobile: +49 177 2345 869 fax: +49 30 23 45 86 95
>> http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Berlin
>> Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194
>>