<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
Historically the Windows version came with the command line cminstall.<BR>
It also looked in the registry for stuff.<BR>
<BR>
<BR>
A GUI installer that is just a glorofied unzipper is easy enough and I agree has some value. I put one together a few weeks ago.<BR>
Something that does a little more to find the compiler/linker or setup a "shortcut" to a command line with environment variables might be nice.<BR>
<BR>
<BR>
>> Even if this proper release is just full binary versions, I think it <BR> >> would make a big difference. These could then be used to make .deb <BR>
<BR>
<BR>
Uploaded-archives already exists, with a bunch of fairly current archives..<BR>
Try them?<BR>
(Thanks to Carson for trying them, wrt cvsup; I'm addressing that.)<BR><BR>
<BR>
>>>>>> Just does qualifies as a release anyway? <<<<<<<<BR>
<BR>
More testing??<BR>
<BR>
<BR>
What are people's thoughts/abilities/experience on getting into:<BR>
*BSD ports -- well, FreeBSD already has ezm3, that counts for something<BR>
Debian, Ubuntu, Suse, Fedora, etc. repositories?<BR>
You need to wrangle an approved developer into submitting the package?<BR>
<BR>
<BR>
Olaf is clearly working on something here -- improving cminstall.<BR>
<BR>
<BR>
I'm working on:<BR>
get cvsup building, this won't take long <BR>
<BR>
<BR>
Debugging the formsedit crash; this might take long.<BR>
<BR>
<BR>
Moving FreeBSD/x86 to new smaller Unix/*.i3 files.<BR>
This shouldn't take long. Bootstrapping from whatever platform I first did yielded invalid assembly. I'm going to try from Cygwin instead before I debug further -- something simple about how the PIC "get PC" stub's section is generated..linkonce or not, I tried editing it with Perl to match C compiler output but got it wrong.<BR>
<BR>
<BR>
This will leave I386_DARWIN, AMD64_DARWIN as the main holdouts -- I don't have hardware for them (yet).<BR>
<BR>
<BR>
Fixing up issues around paths to shared libraries, $ORIGIN, etc.<BR>
- Like, restore buildlocal to old behavior; keep buildglobal with new behavior <BR>
- move FreeBSD/x86 to use $ORIGIN with buildglobal <BR>
<BR>
<BR>
After that, I'll probably introduce new platforms I386_LINUX, I386_FREEBSD, SPARC32_SOLARIS, I386_NT, I386_CYGWIN, I386_MINGW that are equivalent to today's LINUXLIBC6, FreeBSD4, SOLgnu/SOLsun, NT386, NT386GNU, NT386MINGNU.<BR>
<BR>
<BR>
And put together some "boot" archives that factor out C ABI issues, OS major version variants, are very cross buildable, and produce not just cm3, but "everything" -- you compile the C and link on the target system.<BR>
<BR>
<BR>
This way, perhaps, a lot of producing a release can fully automated on one build host.<BR>
<BR>
<BR>
(And after all that, maybe get back to ARM_LINUX_OLDABI_UCLIBC or whatever it should be called...but a new ARM device is en route, maybe ARM_LINUX_NEWABI_GLIBC. :))<BR>
<BR>
<BR>
I also need to get m3gdb and cm3ide into my releases, that's comes before introducing new platform names. This entire list is not required for making a release, but m3gdb and cm3ide probably are.<BR>
<BR>
Some of the uploaded archives should be updated too, such as SPARC32_{LINUX,OPENBSD}.<BR>
<BR>
There's also a bunch of other ports I'd like to get through but they don't block a release.<BR>
<BR>
We should maybe split platforms into "tier 1" and "tier 2".<BR>
Just because I released something, doesn't make it to tier 1. :)<BR>
Tier 2 can be missing from a release or having bugs, without holding up other releases.<BR>
<BR>
<BR>
- Jay<BR>
<BR> <BR>> Date: Thu, 9 Apr 2009 15:28:58 -0500<BR>> From: martinbishop@bellsouth.net<BR>> To: m3devel@elegosoft.com<BR>> Subject: [M3devel] CM3 Release<BR>> <BR>> A few days ago there was more talk of a proper "release" for CM3. I<BR>> think this is very important.<BR>> <BR>> Even if this proper release is just full binary versions, I think it<BR>> would make a big difference. These could then be used to make .deb<BR>> packages for Debian/Ubuntu, and hopefully other Linux/BSD distributions.<BR>> <BR>> Does the Windows version come with an installer? If not, I think it should.<BR>> <BR>> Also, along with easy to install releases, I think a good book/tutorial<BR>> should be available online for Modula-3. We already know Nelson's book<BR>> is caught up with copyright stuff, but I wonder if the same is true for<BR>> Harbison's book?<BR>> <BR>> If neither can be released online, perhaps we should try to improve the<BR>> existing tutorial? (http://www.opencm3.net/doc/tutorial/m3/m3_toc.html)<BR>> <BR>> A lot of people right off Modula-3 as being dead because they don't even<BR>> know that a good, free implementation like CM3 exists. I think the<BR>> above ideas would help.<BR></body>
</html>