<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>> Thus said, providing something smaller may be nice for those<BR>> who keep the sources anyway; perhaps just distribute the core<BR>> packages?<BR><BR>
I provide "min" and "std".<BR>"min" is libm3, m3core, maybe sysutils, and cm3/cm3cg, and mklib (used on all NT386 targets)<BR>
It is enough to build a) small non-gui prorams b) the whole system from source.<BR>
<BR>
I haven't studied the core/base lists to come to some "comfortable" feeling that they are a useful compromise.<BR>
I'll probably just find them to be "arbitrary". Or are they some rational list?<BR>
They are almost identical, which I find suspicious, both in their English names, and in their content.<BR>
I offer the bare minimum or the kitchen sink. :)<BR>
<BR>
The "min" NT386GNU also has symbols in it.<BR>
For NT386, they are separate.<BR>
<BR>
This is a reasonable way to separate symbols with the GNU tools.<BR>
I should maybe start doing that.<BR>
The "symbol" file is just the original file, I think even with all the code (wasteful, but easy), and the symbols are removed from the "main" executable in the usual strip way, and the file name of the other put in it. I don't know if there's also a timestamp/hash/guid.<BR>
<BR>
I'll still see about trimming out the static .libs from "std", though I suppose folks might really be interested in "standalone", and using lots of .libs, and not building the system themselves?? (I always suffer from thinking anything I have learned is then easy for anyone else, such as building this system from source to re-derive any of the files that I pruned out of the archive).<BR>
<BR>
I did prune out all the *.m3 files..<BR>
<BR>
Thanks,<BR>
- Jay<BR><BR><BR>
<HR id=stopSpelling>
<BR>
> Date: Sat, 29 Mar 2008 21:19:54 +0100<BR>> From: wagner@elegosoft.com<BR>> To: m3devel@elegosoft.com<BR>> Subject: Re: [M3devel] new NT386GNU releases<BR>> <BR>> Quoting Jay <jayk123@hotmail.com>:<BR>> <BR>> > I moved these away to "funny" names..that don't show on the web page <BR>> > oops..and replaced them with archives that use Win32 naming <BR>> > conventions (foo.lib, foo.lib.sa, foo.exe, foo.dll). Switching this <BR>> > stuff around is pretty quick and easy.<BR>> ><BR>> > Olaf, I'm using 140meg of diskspace in <BR>> > /var/www/modula3.elegosoft.com/cm3/uploaded-archivesMaybe should a) <BR>> > prune out older archives b) see about making "std" smaller, such as <BR>> > not including all the static .libs, like maybe just m3core.lib.sa <BR>> > and libm3.core.sa in order to build cm3 and mklib. Maybe not making <BR>> > all the static .libs by default as well. Maybe stripping <BR>> > all/many/most of the binaries too. I like having symbols, but most <BR>> > of them go unused most of the time, and they aren't hard to <BR>> > regenerate, as long as you have a consistent repro and don't have to <BR>> > debug something that is "precious".<BR>> <BR>> Don't worry too much about the disk space on birch; there's still<BR>> 98 GB free. If you are providing full binary installation archives,<BR>> they will sure be large.<BR>> <BR>> Thus said, providing something smaller may be nice for those<BR>> who keep the sources anyway; perhaps just distribute the core<BR>> packages?<BR>> <BR>> > I think I'll try deleting all *.lib.sa files except <BR>> > m3core.lib.sa/libm3core.sa -- whatever mklib and cm3 use.<BR>> > And sysutils.<BR>> > Those three files can be crucial in bootstrapping, when an older <BR>> > compiler can't build a newer runtime, but can build a newer <BR>> > compiler, as was the case recently.<BR>> > The native NT386 archives I make are similarly bloated, and even the <BR>> > cminstall archives might be?<BR>> ><BR>> > btw, these are my form of archive. There is no cminstall and nested <BR>> > archive. They extract to cm3-min-posix-5.2.7\bin\cm3.exe and such, <BR>> > which you can then rename or copy into \cm3\bin\cm3.exe or <BR>> > /usr/local/bin/cm3.exe or whatnot, and the config files should just <BR>> > work for pretty much any configuration, as well, you should be able <BR>> > to edit cm3.cfg by just one line to retarget to any of the three <BR>> > NT386/NT386GNU/NT386MINGNU targets, as long as you have the <BR>> > appropriate C build environment setup.<BR>> ><BR>> > Any chance anyone is going to ever use this stuff? :)<BR>> <BR>> I certainly think so.<BR>> <BR>> Olaf<BR>> -- <BR>> Olaf Wagner -- elego Software Solutions GmbH<BR>> Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany<BR>> phone: +49 30 23 45 86 96 mobile: +49 177 2345 869 fax: +49 30 23 45 86 95<BR>> http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Berlin<BR>> Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194<BR>> <BR><BR></body>
</html>