[M3devel] new NT386GNU releases

[Olaf Wagner]

Quoting Jay <jayk123 at hotmail.com>:

> I moved these away to "funny" names..that don't show on the web page  
>  oops..and replaced them with archives that use Win32 naming   
> conventions (foo.lib, foo.lib.sa, foo.exe, foo.dll). Switching this   
> stuff around is pretty quick and easy.
>
> Olaf, I'm using 140meg of diskspace in   
> /var/www/modula3.elegosoft.com/cm3/uploaded-archivesMaybe should a)   
> prune out older archives b) see about making "std" smaller, such as   
> not including all the static .libs, like maybe just m3core.lib.sa   
> and libm3.core.sa in order to build cm3 and mklib. Maybe not making   
> all the static .libs by default as well. Maybe stripping   
> all/many/most of the binaries too. I like having symbols, but most   
> of them go unused most of the time, and they aren't hard to   
> regenerate, as long as you have a consistent repro and don't have to  
>  debug something that is "precious".

Don't worry too much about the disk space on birch; there's still
98 GB free. If you are providing full binary installation archives,
they will sure be large.

Thus said, providing something smaller may be nice for those
who keep the sources anyway; perhaps just distribute the core
packages?

> I think I'll try deleting all *.lib.sa files except   
> m3core.lib.sa/libm3core.sa -- whatever mklib and cm3 use.
> And sysutils.
> Those three files can be crucial in bootstrapping, when an older   
> compiler can't build a newer runtime, but can build a newer   
> compiler, as was the case recently.
> The native NT386 archives I make are similarly bloated, and even the  
>  cminstall archives might be?
>
> btw, these are my form of archive. There is no cminstall and nested   
> archive. They extract to cm3-min-posix-5.2.7\bin\cm3.exe and such,   
> which you can then rename or copy into \cm3\bin\cm3.exe or   
> /usr/local/bin/cm3.exe or whatnot, and the config files should just   
> work for pretty much any configuration, as well, you should be able   
> to edit cm3.cfg by just one line to retarget to any of the three   
> NT386/NT386GNU/NT386MINGNU targets, as long as you have the   
> appropriate C build environment setup.
>
> Any chance anyone is going to ever use this stuff? :)

I certainly think so.

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