SwingWT, Tomcat, Cygwin? [was: Re: Eclipse 3.0.1 on Ubuntu AMD64!]

On Thu, 13 Jan 2005 02:11:32 -0500, Grzegorz B. Prokopski wrote:
 >
 > > How about SwingWT and Tomcat for next release? :-)
 >
 > Well... I thought they should "just work"?  Don't they?

SwingWT hangs and doesn't display anything. At least its not throwing 
exceptions and generally crapping out, so that's an improvement from 
1.1.6 and 1.1.7.

A default configuration of Tomcat 5.0.19 throws a lot of errors and 
refuses connection on several ports specified in the configuration 
files. These ports respond when I use just about any Sun J2SE JDK, 
obviously.

 > If not, please let us know what are the problems and we'll do our best
 > to fix them.

This weekend I'll send you, verbose output for a default install (the 
only thing I changed in the configure step was the --prefix) trying to 
run Tomcat and a few of the SwingWT demos . Let me know if there is any 
other output I could send, or if I should rebuild SableVM with a 
specific set of configure parameters. Should I send the verbose output 
here or to sablevm-devel?

 > > PS - What's the status on Cygwin port?
 >
 > Good question.  I got the impression there were people seriously
 > interested in having Cygwin supported, there even was a version that
 > actually was packaged for cygwin, but I have not tracked it further.

Yes, sablevm-1.16 binaries and source were packaged up by a third-party 
at some point, but there's been nothing since, and sablevm is not part 
of Cygwin (would be nice if they took up maintenance of the port :-)

There probably are many many people interested in Cygwin support, but 
not many are coming forward to get it done. I really would like to have 
that happen, so I'm stepping forward to help as I can.

 > Does anyone care to bring us up to date with what's happening to Cygwin
 > support?  Does it work out-of-the-box?  Any pending patches?

Most of the discussion months ago centered on the problem of compiling 
libffi as a Cygwin DLL. Hopefully someone will fill us in on the scary 
details, so that we can tackle them for 1.1.8 and carry the port forward 
from now on.

If someone could explain what needs to be done, I willing to help make 
sure Cygwin support doesn't break, by making frequent (weekly?) SVN 
snapshot builds, hosting them, run some sort of unit tests on the builds 
(mauve?) and reporting errors to SableVM-devel.

I could also help with Mac OS X once I set up my Mac with the 
development environment this weekend (the hard disk had crashed and it 
was "recuperating" at the Cupertino PowerBook Convalescence Center, aka 
AppleCare. :-) Someone is going to have to help me if OS X also has 
build issues. IIRC, Mac OS X sometimes also acts funny with shared 
libraries, similar to how Cygwin doesn't automatically build libs as DLLs.

Later,

PJ Cabrera