Building GCC 3.3 / MingW: The Saga Continues

[Mohan Embar <gnustuff at thisiscool dot com>]

Hi folks,

Thanks to Lars' build tips for building GCC 3.3 / MingW:

http://gcc.gnu.org/ml/java/2003-02/msg00134.html

I was able to build the cross compiler too. Rather than messing around
with the crossed native compiler, I first decided to see if I could
build a Win32 "Hello, world" program from Linux. This worked. Then
I modified, the libswt.a build shell script from:

http://gcc.gnu.org/ml/java/2002-12/msg00105.html

and built a Win32 libswt.a from Linux.

I then built the Hello.java SWT example from:

http://www-106.ibm.com/developerworks/library/j-nativegui/
(Listing 2)

and ran in on Windows. It crashed with:

Exception in thread "main" java.lang.UnknownError: Runtime.loadLibrary not
implemented
   at 0x005260bc (Unknown Source)
   at 0x00525bdc (Unknown Source)
(etc.)

I'll look into this later.

Tom> I think in the long term the plan is to separate out the Windows
Tom> java.net native code into its own files.  My understanding is that
Tom> sharing the code here is not practical.

How impractical is this? Could someone educate me? Given the large
amount of code sharing made possible with MS's BSD-layer-wannabe 
implementation, although imperfect, wouldn't creating two parallel code sets
create a maintenance headache?

To my knowledge, a formal patch was never created for

Ranjit's suggestion:
http://gcc.gnu.org/ml/java/2002-12/msg00295.html

with Tom's naming convention factored in:
http://gcc.gnu.org/ml/java/2002-12/msg00320.html

Are we still okay with this approach? I wouldn't mind submitting
a patch for this if everyone was okay with it. (I'd have to read
up how to formally submit a patch, but I'm game for this.)

Thanks again for all your untiring efforts.

-- Mohan