On 24/12/2017 9:01 PM, Ted Neward wrote:
So if I do a "make hotspot" it replaces the compiled Hotspot binary in the
exploded build image?
I believe so, but simplest thing is to do a find for libjvm.so before
and after the "make hotspot" and see which one(s) changed.
David
The reason I ask is that this is what I tried, and it didn’t appear to show up in the
list of "PrintFlagsFinal" output.
Ted Neward
Author, Speaker, Mentor
http://www.newardassociates.com
t: @tedneward | m: (425) 647-4526
On 12/22/17, 12:32 AM, "Erik Joelsson" <erik.joels...@oracle.com> wrote:
On 2017-12-22 01:06, David Holmes wrote:
>
> "make hotspot" won't update the image, you need to "make images" for
> that.
>
> Assuming you're building 9+ then when you change libjvm.so the module
> needs to be rebuilt etc.
>
> Or you can work from the exploded build the contents of e.g.
>
> build/linux-x64-debug/jdk/
>
> though you still need a full build to prime that. But after that "make
> hotspot" should suffice. (Erik correct me if I'm wrong here please.)
This is correct. Using the exploded image as described is the shortcut
we have. The actual images are always built using jmod/jlink and yes,
that requires quite a bit of extra build time.
If you are in JDK 8, you need to run "make jdk" to get the exploded
image updated with the new libjvm.so.
/Erik
