[M3devel] NT386GNU distribution available

[Darko]

Do you have a link for the distribution, or did I miss something?

- Darko

On 21/01/2008, at 8:41 AM, Jay wrote:

> Here, in my user directory on birch, is the first CM3 NT386GNU  
> release.
> It is MinGWin based FOR NOW.
> This needs to be changed SOON.
>
> Install MinGWin. (Search the web for it.)
> set PATH=c:\MinGW\bin;%PATH%
>
> (The default install location is c:\MinGW, not MinGWin.)
>
> The MinGWin that Qt gives you is too old, from around 2004.
> It doesn't support "response files" (aka long command lines).
>
> If you want to rebuild m3cg:
>
>   Install MSys. It is at the same place as MinGWin.
>   set PATH=c:\msys\1.0\bin;%PATH%
>
> else consider
>
>   set OMIT_GCC=yes
>
> depending on if you run the various scripts.
>
> If you install to these exact paths, scripts\python\pylib.py
>   will use them automatically.
>
> Optionally install Python. I recommend it.
>
> Extract one or more of the archives.
> They will extract to like:
>
>   cm3-min-WIN32-NT386GNU-d5.5.1\bin\cm3.exe
>
> You can rename it cm3, or for purposes of backup/restore,
>  xcopy /fivery \cm3-min-WIN32-NT386GNU-d5.5.1 \cm3
>
> (For extra good testing, first rmdir /q/s \cm3.)
>
> set PATH=c:\cm3\bin;%PATH%
>
> This is important, since various code will tend to assume NT386  
> unless overridden.
>
> set CM3_TARGET=NT386GNU
>
> Someone please weigh in on zip vs. tar.bz2 on the other Win32  
> platforms.
> For reference, MinGWin doesn't include tar/bzip2, MSys does, Cygwin
> has tons of optional stuff, they are in there, probably the base.
>
> And then go to scripts\python and run whatever:
>   upgrade
>   or make-dist
>   or do-cm3-core
>   or do-cm3-base
>   but not currently do-cm3-std
>
> scripts\win\upgrade works too.
>
> Do remember to set CM3_TARGET=NT386GNU.
>
> You will probably at some point be prompted to set CM3_ROOT to the  
> root of the source
> tree as well. If you run "scripts", it will be set for you.
> If you cd around and run cm3, it won't.
>
> \cm3\bin\cm3.cfg delegates out to the source tree.
> Except the one in the distributions do not.
> But if you run upgrade, you'll have such a thing.
>
> If you want to rebuild cm3cg from source:
>   cd m3-sys\m3cc\gcc\gcc\m3cg
>   cvs update -j 1.46 -j 1.45 parse.c
>
> or thereabouts to get back enough of a __stdcall fix to build a lot.
>
> If you want to bootstrap without a previous NT386GNU distribution  
> but with
>   a previous NT386 build, try like this:
>
>   Get a working NT386 system.
>   Get current source (except parse.c).
>   If your system is not current,
>       scripts\python\upgrade
>       This will work as far back as cm3-min-WIN32-NT386-5.1.3.
>   scripts\python\bootntgnu
>       which is really just roughly:
>       do-pkg realclean m3core libm3 m3cc
>       do-pkg buildship m3core libm3 m3cc
>       set CM3_TARGET=NT386GNU
>       Now you have the equivalent of the minimum distribution and  
> can build whatever.
>       do-pkg ....
>
>   If you want to rollback a bit but not completely, scripts\win 
> \pkggnu_clean.cmd is
>     very simple and just deletes all the NT386GNU directories under  
> $INSTALLROOT\pkg.
>
> There are "min", "core", and "base" distributions.
> Kind of subtle names, eh?
> "min" is sufficient.
> The binaries are all not "strippped".
>
> Last minute errata:
>  There is bin\cm3.cfg and bin\NT386GNU. They are identical.
>  The intent was only to have cm3.cfg there.
>
> The system builds itself, so that's pretty good.
>
> I forgot to include m3gdb, but it should probably be in a separate  
> "GNU" archive?
>
> Someone move the files to a web download place?
> (and you can move, not copy, I can easily recreate the files)
>
>  - Jay
>
> Shed those extra pounds with MSN and The Biggest Loser! Learn more.