Re: E 0.9.3 release?

On Mon, 2011-01-03 at 19:27 -0800, Mark Miller wrote:
> Commit notice on subversion r793, available at
> <http://www.erights.org/download/0-9-3/>
> 
> 
> --------------------------------
> Candidate 0.9.3b release
> 
> 
> Per advice at
> http://www.eros-os.org/pipermail/e-lang/2011-January/013712.html
> removed the suppression of "-Werror" and the bogus "(int)" cast.
> Instead, changed virtually all "char" declarations to "unsigned
> char". It compiles fine now with no warnings.
> 
> 
> Since 
>   * E does not auto-install on Windows 7 (and probably never did, and 
>     perhaps not on Vista either), 
>   * no one is actually using this Windows-specific installation
> feature
>     http://www.eros-os.org/pipermail/e-lang/2011-January/013713.html 
>     (setting up the registry, etc),
>   * 
> I am deleting the src/csrc/utils, src/csrc/win32, and
> src/csrc/win32/setup directories and changing the code
> (src/esrc/scripts/setup.e-awt) and documentation
> (src/csrc/setup/README.txt) that depends on them to no longer do so.
> Also changing the Makefiles so that making no longer traverses into
> the deleted directories.
> --------------------------------
> 
> 
> 
> On Mon, Jan 3, 2011 at 12:08 AM, Thomas Leonard <[email protected]>
> wrote:
>         On 2 January 2011 06:12, Mark Miller <[email protected]>
>         wrote:
>         > Hi Thomas,
>         > In order to warm up the old release muscles, I tried
>         building a new 0.9.3a
>         > candidate on Windows
>         <http://www.erights.org/download/0-9-3/>. (E does not
>         > cross build. The binary for each platform must be built on
>         that platform.)
>         
>         [...]
>         > Windows Vista or 7 problems (i.e., since Windows XP):
>         > I can build E fine on Windows 7. However, when I try to
>         install it on
>         > Windows 7, I get a bunch of (quite sensible) permissions
>         violation errors
>         > when I try to manipulate the registry. No annoying Windows 7
>         "do you really
>         > mean it?" monologue boxes, just errors. However, when I
>         install this same
>         > binary on Windows XP, it works as well as it always did.
>         >
>         > If anyone knows of a simple fix to get old cygwin/gcc C code
>         for
>         > manipulating the XP registry to work again on Windows 7,
>         please let me know.
>         > Assuming this doesn't work out easily, I'm inclined to pull
>         all the registry
>         > magic from the E installation. Would this inconvenience
>         anyone? Does anyone
>         > still care about, for example, the binding of the ".e"
>         extension to the E
>         > launching behavior?
>         
>         
>         That's no problem for us. I hadn't even realised there was a
>         Windows
>         installer!
> 
> 
> Prior to today's commit, it was documented in the README.txt file.
> Basically, it said to do an automatic install on Windows either by
> double clicking e.jar or by running "java -jar e.jar" on a command
> line.
> 
> 
>  
>         I've seen Windows devs at work install E, and as I recall
>         the steps they use are:
>         
>         1. unpack the E release zip archive somewhere
>         2. set the E_HOME system variable to that location
>         3. replace swt.jar with a different one (64-bit issue?)
> 
> 
> I'm running E fine on a 64-bit Windows 7 system without replacing the
> swt.jar file. Can you say more about this issue?

I guess it depends on whether you're using the 64-bit version of Java
with it. Looks like there's a similar issue on Macs:

http://thread.gmane.org/gmane.comp.lang.e.general/4521/focus=3633

Probably the solution here is to not bundle SWT at all. Anyone who wants
to write a SWT application will have to add it to classpath themselves
(following the normal Java/SWT documentation for this).

The only problem I see here is that the taming database might get out of
sync with the version of SWT being used. On the other hand, being able
to upgrade SWT independently of E for bug-fixes is useful too.


-- 
Dr Thomas Leonard
IT Innovation Centre
2 Venture Road
Southampton
Hampshire SO16 7NP

Tel: +44 0 23 8076 0834
Fax: +44 0 23 8076 0833
mailto:tal-v5nx5w6akNyLE8xUarVfuPLx9OUvmyODWmv/[email protected]
http://www.it-innovation.soton.ac.uk