Re: Step-By-Step Build Instructions for MinGW gcc/gcj 3.4 Compilers

[Mohan Embar <gnustuff at thisiscool dot com>]

Hi Erik,

>> Wouldn't this be the ideal SWT demo app you're looking for?: [Get Sources],
>> [Build],[Clean], [Clean Build], [Install], [All About Erik, The Amazing GCJ SWT
>> Coder].
>
>It would be an interesting excercise. 
>
>However, I'd rather create GUIs for non-computer literate end users than for fellow
>developers. The target I have in mind, is to facilitate the work for developers to
>create GUIs for end-users. 
>
>Developers themselves should rather be assisted by teaching them how to script tasks
>and generally facilitate their work by automating stuff.

Okay, I see you're point. I was sort of suspecting you'd feel this way.

>> 3.3 is more problematic. You need a cross-configury patch and updated configure
>> scripts if you want to avoid installing automake and autoconf. I'll follow up
>> on this later.
>
>Ok. If 3.4 works substantially better than 3.3 without introducing serious issues,
>I'm definitely interested in moving (again) to snapshots.

>If there is a really good case for moving to 3.4 (such as fewer patches and stuff
>like that) and no nasty issues attached, I'm ok with 3.4. It's an issue of judgment
>(which I don't have in this matter). How do you see it?

I don't know enough about gcc internals, libstdc++ stability, etc. to comment
on this. However, I know that my networking cleanup patch (which will be slightly
redone, but will stay the same in spirit) substantially improves the networking
stuff on MinGW, especially in the area of error handling. I don't know whether
there are other libjava regressions or stuff like that. 3.4 is in a constant state
of flux.

However, adding a Windows tester base will certainly help 3.4 out, and from
the little I've seen it seems okay. This could change from one day to the next,
though.

-- Mohan
http://www.thisiscool.com/
http://www.animalsong.org/