Le roi est mort, vive le roi!
Staffan Larsen
staffan.larsen at oracle.com
Mon Nov 25 07:53:51 UTC 2013
On 25 nov 2013, at 08:02, Francis ANDRE <francis.andre.kampbell at orange.fr> wrote:
> David
>
> Le 25/11/2013 02:55, David Holmes a écrit :
>> On 25/11/2013 1:46 AM, Francis ANDRE wrote:
>>> Mike
>>> Le 19/11/2013 19:14, Mike Duigou a écrit :
>>>> Early in jdk8 development it used the same build system as jdk7. A new
>>>> build system was developed and eventually replaced the "old" build
>>>> system. The removal in this changeset removed the obsolete legacy
>>>> build system. There are no plans to backport the new build system to
>>>> java 7.
>>> Just to confirm my understanding, when Magnus or yourself speak about
>>> the old system as the jdk7 one, you are talking about the build of the
>>> subdirectory jdk8/jdk because the jdk8/hotspot is the same as in jdk7.
>>
>> Not quite. The hotspot build system was not rewritten to require the configure-based top-level build, but it was modified to be aware of, and work with, a configure-based top-level build. A lot of hotspot developers only build hotspot, not the full JDK.
> So David, how do they test their changes to hotspot?? with jtreg? another tool?
>>
>>> By the way, I am wondering in the "new" system how you are planning the
>>> support the create.bat and the generation of the jcm.vxproj by
>>> ProjectCreator. VisualStudio C++ is a mandatory tool for testing,
>>> understanding and debugging hotspot. So what about the "old" hotspot
>>> build under jdk8?
>>
>> Updates to those windows specific parts of the hotspot build have taken place as problems are detected. If there is something specific that is currently an issue then a bug needs to be filed against hotspot->build. The hotspot team generally handles this not the "build team".
> The top level make produces a full jdk here : Z:\JDK\jdk8\build\windows-x86-normal-server-release\images\j2sdk-image
> The hotspot make produces a full jdk here : Z:\JDK\jdk8\hotspot\build\windows\jdk-windows-i586
> The hotspot create.bat produces a JVM here: Z:\JDK\jdk8\hotspot\build\vs-i486\compiler1
>
> create.bat has only one parameter: the bootstrap jdk and thus does not take into account the configure-based top-level files. Moreover when using an official public jdk7 release as the jdk1.7.0_45 as the bootstrap jdk of jdk8, the produced jvm.vxproj does not work as the changeset associated with the JDK 8016019 are not back ported to the jdk1.7.0_45 release. So I am wondering what specific parameters hotspot developers are using to test their changes under WXP/W7 for the jdk8 hotspot?
The visual studio projects are not the official way to build hotspot. They are provided as a nice-to-have feature that developers on windows maintain. The official way to build on all platforms is to use the makefiles.
/Staffan
> Francis
>>
>> David
>> -----
>>
>>>
>>> Francis
>>>>
>>>>> the jdk8 build system, but what is the old one?
>>>>>
>>>>> Francis
>>>>>
>>>>> Le 18/11/2013 19:02, Magnus Ihse Bursie a écrit :
>>>>>> So, finally it has happened. The old build system is now removed.
>>>>>> The patch was just submitted to the tl forest, from where it will
>>>>>> move to master in a few days.
>>>>>>
>>>>>> If you have personal scripts that are using hard-coded makefile
>>>>>> references, you might need to update them.
>>>>>>
>>>>>> Thanks to everyone who helped this major project become reality:
>>>>>> Fredrik, Erik, Kelly, Tim, Jonas, ...
>>>>>>
>>>>>> /Magnus
More information about the build-dev
mailing list