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

On Jan 14, 2005, at 8:48 AM, PJ Cabrera wrote:

> <snip>
> > > 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.

Gerrit set up a Cygwin build for 1.1.6, which included the libffi 
changes necessary to get that working for Cygwin. I did some work after 
that for a mingw version. That project made quite a bit of progress but 
I have had to set it aside for now.



> 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.

I have routinely been building on Mac OS X (my main dev system) and 
things "just work". One side note - what I'm doing is non-GUI so I'm 
always building with --disable-gtk-peer

The recent version 1.1.8 includes a script to check whether all the jni 
methods are present, and that script fails. The methods are there but 
the check is broken. I think it's a problem with "\w" in sed but I 
haven't had enough time to find out for sure. Interestingly, all the 
names which fail contain a digit. This script, as written, also dies on 
freebsd53 because the tools there aren't gnu-like and the script 
doesn't compensate (it's fixed and not generated by auto*). For the 
time being you can just remove the testing in the script -- all the 
methods are present in the distribution.

I wonder if the script-test should not actually be part of the 
distribution, but only done as part of the preparation to build it?

Regards.....Peter

p.s. no answers next week as I'll be away