Re: Le roi est mort, vive le roi!
* Magnus Ihse Bursie magnus.ihse.bur...@oracle.com [2013-11-18 13:19]: 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. Congrats! This is fantastic news! Cheers, Omair -- PGP Key: 66484681 (http://pgp.mit.edu/) Fingerprint = F072 555B 0A17 3957 4E95 0056 F286 F14F 6648 4681
Re: Le roi est mort, vive le roi!
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
Re: Le roi est mort, vive le roi!
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
Re: Le roi est mort, vive le roi!
David 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? Most developers don't use create.bat or the vs projects. I am desesperated by your remark, really David - 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
Re: Le roi est mort, vive le roi!
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
Re: Le roi est mort, vive le roi!
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
Re: Le roi est mort, vive le roi!
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. 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? 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
Re: Le roi est mort, vive le roi!
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. 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. 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
Re: Le roi est mort, vive le roi!
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? 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
Re: Le roi est mort, vive le roi!
On 25 nov 2013, at 08:02, Francis ANDRE francis.andre.kampb...@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
Re: Le roi est mort, vive le roi!
Magnus By the way, what is exactly the old build system??? I am aware of the jdk7u build system, 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
Re: Le roi est mort, vive le roi!
On Nov 19 2013, at 09:26 , Francis ANDRE francis.andre.kampb...@orange.fr wrote: Magnus By the way, what is exactly the old build system??? I am aware of the jdk7u build system, 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. 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
Re: Le roi est mort, vive le roi!
Oh, I can't find the I Like button anywhere in the mailer :) Cheers, Mario 2013/11/18 Magnus Ihse Bursie magnus.ihse.bur...@oracle.com 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 -- pgp key: http://subkeys.pgp.net/ PGP Key ID: 80F240CF Fingerprint: BA39 9666 94EC 8B73 27FA FC7C 4086 63E3 80F2 40CF IcedRobot: www.icedrobot.org Proud GNU Classpath developer: http://www.classpath.org/ Read About us at: http://planet.classpath.org OpenJDK: http://openjdk.java.net/projects/caciocavallo/ Please, support open standards: http://endsoftpatents.org/
Re: Le roi est mort, vive le roi!
Ok, but does this mean that no one is interested in fixing the old jdk7u system? (I posted an help message about [7u]: help on jdk/make/common/shared/Defs-windows.gmk and got no answer, while the fix I am proposing will make the build in jdk7u easier by fixing this error ERROR: Trouble with the absolute path for OUTPUTDIR!!) Francis Le 19/11/2013 19:14, Mike Duigou a écrit : On Nov 19 2013, at 09:26 , Francis ANDRE francis.andre.kampb...@orange.fr wrote: Magnus By the way, what is exactly the old build system??? I am aware of the jdk7u build system, 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. 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
Re: Le roi est mort, vive le roi!
I found an appropriate tombstone: -kto On Nov 18, 2013, at 10:02 AM, Magnus Ihse Bursie wrote: 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
Re: Le roi est mort, vive le roi!
2013/11/18 2:02 -0800, magnus.ihse.bur...@oracle.com: So, finally it has happened. The old build system is now removed. ... Huzzah! - Mark
Re: Le roi est mort, vive le roi!
On Nov 18, 2013, at 10:49 AM, Kelly O'Hair wrote: I found an appropriate tombstone: -kto On Nov 18, 2013, at 10:02 AM, Magnus Ihse Bursie wrote: 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
