I wasn’t implying that it would go away, merely that it is a second class citizen compared to the makefiles.
/Staffan On 26 nov 2013, at 20:29, Erik Gahlin <erik.gah...@oracle.com> wrote: > I know 5-10 Hotspot developers who uses Visual Studio (me included) so I hope > it's not something that is going away. > > Erik > > Staffan Larsen skrev 2013-11-26 20:10: >> I am in full agreement with you that an IDE is a very powerful tool and I >> much prefer to work in an IDE than outside one. However, I do not do my >> day-to-day work on Windows (anymore - I used to). I don’t know how >> developers on Windows manage their work. >> >> /Staffan >> >> On 26 nov 2013, at 18:34, Francis ANDRE <francis.andre.kampb...@orange.fr> >> wrote: >> >>> Hi Staffan >>> Le 25/11/2013 08:53, Staffan Larsen a écrit : >>>> >>>>> 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, while the official way to build on all platforms is to use the >>> makefiles, it does not make sense when talking about debugging, testing and >>> developing a major, large, multi layered C++ application like hotspot. >>> >>> To make it short, VisualStudio C++ is to c++ what Netbeans or Eclipse are >>> for Java, a mandatory powerful IDE for developping large and complex >>> application. Can you image to code, develop, debug, test a multi-threaded >>> java application fo 250 kilo lines without Netbeans, just with vi, >>> makefiles and some additional tools... I do not think so... So, it is the >>> same for hotspot on WXP/W7! >>> >>> Thus, if as I understand well, WXP/W7/ X86/X64 are strategic platfoms for >>> Oracle in providing a fully certified and supported Java environment, then >>> the nice-to-have feature is not at level of the mission. The generation of >>> the jvm.vxproj cannot be a second level citizen but should be as good as >>> the generation of the jdk, fully maintained and integrated as new features, >>> way fo building "the new build system" and so on are added, modified or >>> deleted.... >>> >>> Francis >>> >>>> /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 >
