[M3devel] CM3 Release

[Jay]

Historically the Windows version came with the command line cminstall.

It also looked in the registry for stuff.

 

 

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.

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.

 

 

 >> Even if this proper release is just full binary versions, I think it 
 >> would make a big difference. These could then be used to make .deb 

 

 

Uploaded-archives already exists, with a bunch of fairly current archives..

Try them?

(Thanks to Carson for trying them, wrt cvsup; I'm addressing that.)


 

>>>>>> Just does qualifies as a release anyway? <<<<<<<

 

More testing??

 

 

What are people's thoughts/abilities/experience on getting into:

 *BSD ports -- well, FreeBSD already has ezm3, that counts for something

 Debian, Ubuntu, Suse, Fedora, etc. repositories?

 You need to wrangle an approved developer into submitting the package?

 

 

Olaf is clearly working on something here -- improving cminstall.

 

 

I'm working on:

  get cvsup building, this won't take long 

 

 

  Debugging the formsedit crash; this might take long.

 

 

  Moving FreeBSD/x86 to new smaller Unix/*.i3 files.

    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.

 

 

    This will leave I386_DARWIN, AMD64_DARWIN as the main holdouts -- I don't have hardware for them (yet).

 

 

  Fixing up issues around paths to shared libraries, $ORIGIN, etc.

     - Like, restore buildlocal to old behavior; keep buildglobal with new behavior 

     - move FreeBSD/x86 to use $ORIGIN with buildglobal 

 

 

  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.

 

 

  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.

 

 

  This way, perhaps, a lot of producing a release can fully automated on one build host.

 

 

  (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. :))

 

 

 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.

 

Some of the uploaded archives should be updated too, such as SPARC32_{LINUX,OPENBSD}.

 

There's also a bunch of other ports I'd like to get through but they don't block a release.

 

We should maybe split platforms into "tier 1" and "tier 2".

Just because I released something, doesn't make it to tier 1. :)

Tier 2 can be missing from a release or having bugs, without holding up other releases.

 

 

 - Jay


 
> Date: Thu, 9 Apr 2009 15:28:58 -0500
> From: martinbishop at bellsouth.net
> To: m3devel at elegosoft.com
> Subject: [M3devel] CM3 Release
> 
> A few days ago there was more talk of a proper "release" for CM3. I
> think this is very important.
> 
> Even if this proper release is just full binary versions, I think it
> would make a big difference. These could then be used to make .deb
> packages for Debian/Ubuntu, and hopefully other Linux/BSD distributions.
> 
> Does the Windows version come with an installer? If not, I think it should.
> 
> Also, along with easy to install releases, I think a good book/tutorial
> should be available online for Modula-3. We already know Nelson's book
> is caught up with copyright stuff, but I wonder if the same is true for
> Harbison's book?
> 
> If neither can be released online, perhaps we should try to improve the
> existing tutorial? (http://www.opencm3.net/doc/tutorial/m3/m3_toc.html)
> 
> A lot of people right off Modula-3 as being dead because they don't even
> know that a good, free implementation like CM3 exists. I think the
> above ideas would help.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20090409/c632299f/attachment-0002.html>