[M3devel] move to version 5.7.1?

[Jay]

I meant, can we update the version stamp in the compiler.
Nothing about releases or what not.
But I'll take some of the bait. :)
 

My archives are already pretty easy to use, but need a short readme.
 

HP-UX is not yet supported, but will be fairly soon, maybe this week.
64bit first, this week, then 32bit, by end of next week?
(HP-UX also runs on IA64 btw, but I couldn't get my hardware to boot
my OS, maybe too old OS, maybe need to fiddle with EFI console settings.
I will be doing IA64_LINUX before long. IA64_FREEBSD also wouldn't boot
for me.)
 

Where is the line between "free Microsoft tools" and "free Python"?
 

Python is NOT needed to build cm3, just as bash is not needed.
 

There are VERY handy scripts for doing so, in both languages.
They are just slightly elaborate ways to cd around and run cm3.
 

I know, I know..they are each line crossing, everything I have to
install is a line. If it was just "free Python" and no need for "free Microsoft",
that would be similar as just "free Microsoft". And "free Microsoft"
is higher quality and more trusted than "free Python", and, clearly,
simply more necessary, unless you use Cygwin.

 
Cmd is an awful language for nearly any purpose.
Please don't ask me to support any cmd files.
 

Maybe I will rewrite the automation in JScript.
It is a half decent language and works plenty well for command line automation.
It is been "in the OS" for many years, probably at least since Windows 2000, and
with any install of Internet Explorer.

 
But really..you know..all the Python I write...is somewhat of an indictment
of either Modula-3 or myself -- I don't "like" Modula-3 enough to write much
of anything in it.. That is..these "scripts" perhaps should be written in Modula-3.
 

Or maybe actually in Quake?
Quake is kind of limited though.
Maybe with the updates though that Olaf made?
I'll think about it.
 

The system is "easier" to build from a "current" system than from an "older" system.
upgrade.sh and upgrade.py work with either.
If your system is already current, you can just build in dependency order.
If your system is not current, you first build "just the compiler", in dependency
order, but skipping and m3core, libm3. Or you possibly hack them slightly.
(Btw Tony there are few other instances of LONGINT in m3core than the one, but not many.)
 
 
Most of this confusion is probably only for people that build the system.
As well, maybe it could be reduced by just having an "output root"
like I've said, but I know that'd be disruptive.
 

The archives I upload are not bad.
You just extract them, set $PATH, install Python, get/install a
C compiler and linker and runtime (either Cygwin or Microsoft) and go.

 
I think they are better than the cminstall-based ones.

 
I am not likely to get around to much additional polish.
 
 

 - Jay



________________________________
> Date: Mon, 19 Jan 2009 18:50:40 -0500
> From: rcoleburn at scires.com
> To: m3devel at elegosoft.com
> Subject: Re: [M3devel] move to version 5.7.1?
>
>
>
>
>
>
>
> Jay et al:
>
>
>
> I have not updated any of my cm3 code base since I released my last application to my customer in late 3Q2008.
>
>
>
> Based on all the activity, I don't think I want to do an update until we've decided to make a new release. This decision should be based primarily on stability of the code base across platforms.
>
>
>
> I can backup my cm3 tree, update to latest code, and run tests on Windows XP using my current apps if that would be helpful. Let me know. Also, I may be able to do some tests on HP-UX if that platform is supported. In addition, I also now have access to a Solaris box.
>
>
>
> One of the things I want to do for the next release is to provide detailed documentation on how to install cm3 on Windows using just the tools that comes with Windows or that are available free from Microsoft. I've already got a good start on this, but will want to get input on the exact order of package builds and which have to be repeated when.
>
>
>
> My idea is that we should have a minimal install archive for Windows (NT386) available from which the "customer" (end-user) can build all of the supported packages in the correct order, including rebuilding the base/core cm3 to prove his system is fully functional. On Windows, the build would be handled via .CMD files and not require python or anything else not supplied with Windows or free from Microsoft.
>
>
>
> I also want "us" to give explicit, documented, definitions of the terms "build", "ship", "clean", "spotless", etc. etc. that are used in various scripts et al and make these consistent. We also need to have good documentation on all the pragmas, environment variables, options, and command line switches that CM3 and CM3IDE recognize. I believe a number of these currently exist that are not well-known or properly documented.
>
>
>
> IMO, this next release needs to be as professional as possible and provide end users (customers) with the best possible experience in terms of ease of installation and use.
>
>
>
> I'll help as much as I can.
>
>
>
> Regards,
>
> Randy Coleburn
>
>>>> Jay 1/19/2009 5:39 PM>>>
>
> Should we move to move version 5.7.1?
>
> To mark the new year, and NT386GNU defaulting to pthreads (I'm thinking I should go back and make it a command line option, it's very very easy).
>
> Just edit two lines in sysinfo.sh and everything keeps working, right?
>
> - Jay