How to test a fresh HotSpot build on Windows without building the whole JDK?

[Tom Rodriguez]

That's a reasonable way to test your built jvm.dll so I would suspect  
some build problem.  Did you build it using the generated project file  
inside VS or make/windows/build.bat?  It's possible there are some  
issues with the generated project file.  The machinery for generating  
that is separate from our normal make process so it will sometimes be  
broken until some one notices it.  You might compare the symbol  
exports between your build and the standard one.

tom

On Nov 19, 2008, at 2:08 AM, Volker Simonis wrote:

> Hi,
>
> I've just built a 64-bit debug HotSpot on Windows and I realized that
> under Windows there's no "gamma" launcher like under Linux/Solaris
> which can be used to run a freshly build HotSpot with an existing JDK
> by setting the JAVA_HOME environment variable. The quick hack of just
> replacing the "jvm.dll" (together with "jvm.map" and "jvm.pdb") of a
> recent 64-bit Java 7 debug release (b39) with my newly build versions
> of these files didn't work either:
>
> Error: loading: d:\Software\jdk1.7.0_x64_b39\jre\bin\server\jvm.dll
>
> Is there a simple way how one can run a freshly build  HotSpot on
> Windows without building the whole JDK?
>
> I should also mention that I built the HotSpot with VS 2005 which to
> my knowledge is different from the version that was used to build the
> Java 7 binaries. May this be a problem?
>
> Any suggestions are highly welcome.
>
> Volker