Errors in windows build?

[Kelly O'Hair]

It's been my experience that it's almost impossible to say for sure that
all Windows users will be able to build.
All we can say is that in one particular case, we know it builds.
There are just too many variations with a Windows system's configuration
and all the versions of CYGWIN PSDK OS etc.
Normally we nail down our Windows build systems once we get them
configured and working. Linux and Solaris is much easier to deal with.

But I think I understand what you are after, so I will try a build myself
once we have the windows binary plugs created.
Give me a few days.

I'm not exactly sure what the QA procedures are, but we explicitly
ruled out any QA Windows OpenJDK build testing initially.
The fact that the VS003 compiler on Windows has to be purchased
makes it difficult for the QA testing, normally QA people don't have to
"compile" anything. ;^)
Someday soon we can get it going with the free VS2005 compilers, but for
now you really need VS2003.

-kto

Dan Fabulich wrote:
> 
> Thanks for your remarks, Kelly.
> 
> I'd like to make a remark/request here.  It's clear that the Windows 
> OpenJDK build didn't go through any QA, in light of the fact that it 
> can't possibly succeed without t2k.lib.  In light of that, I'd say that 
> there's no reason to assume that the rest of the build works as 
> documented, either.  There could well be bugs in the build scripts or in 
> the documentation that make it impossible to complete the build.
> 
> Would it be possible for someone at Sun (ideally a QA engineer) to grab 
> a copy of the real binary plugs, add a copy of t2k.lib in the 
> appropriate directory and then build OpenJDK following the directions 
> from the README, (using Cygwin rather than MKS, etc.)?
> 
> What I'm looking for is for someone at Sun to say "works for me!" 
> Nobody's said that yet in any e-mail that I can find, and that worries me.
> 
> -Dan