<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
On 23/03/12 19:11, Fredrik Öhrström wrote:
<blockquote
cite="mid:CALZT+jASpi5_+KJQu0Gj6h_4NZyGqRJ-LV+fSLuFN-sWpfhy=A@mail.gmail.com"
type="cite">in increasing order of verbosity<br>
<br>
make VERBOSE=<br>
make VERBOSE=-d<br>
make VERBOSE="-d -p"<br>
<br>
</blockquote>
Thanks. It looks like the first of the three options above is most
similar to the verbosity<br>
level of the old build. Is all of this documented anywhere?<br>
<br>
I think at the very least, a cheat-sheet will be needed to help
people transition between<br>
the two systems, and options like the first one above will be very
commonly used as part of that.<br>
Maybe an actual flag value for that setting (as opposed to the empty
string) might be more<br>
meaningful.<br>
<br>
Another minor (newbie) comment, is that some of the configure flags
are documented (in --help)<br>
as --with-XXX=PATH, but there are some that should be documented the
same way, but aren't<br>
(--with-boot-jdk is the one many will see first)<br>
<br>
- Michael<br>
<blockquote
cite="mid:CALZT+jASpi5_+KJQu0Gj6h_4NZyGqRJ-LV+fSLuFN-sWpfhy=A@mail.gmail.com"
type="cite">Den fredagen den 23:e mars 2012 skrev Michael
McMahon<<a moz-do-not-send="true"
href="mailto:michael.x.mcmahon@oracle.com">michael.x.mcmahon@oracle.com</a>>:<br>
> Is it possible to get a more verbose style of echoing the
complete compile/build commands<br>
> like the old build ?<br>
><br>
> - Michael<br>
><br>
> On 21/03/12 14:07, Erik Joelsson wrote:<br>
><br>
> As outlined in [1], the build-infra project would like to
push the current work into jdk8 in order to expose it to a wider
audience. The webrevs are made against the jdk8/build forest. In
each repository, there are two kinds of changes:<br>
><br>
> 1. Changes to old makefiles and source code to be compatible
with the new build.<br>
> 2. The new makefiles<br>
><br>
> For corba, jaxp and jaxws, all changes of category 1 have
already gone in. For langtools, we are awaiting one more change
for introducing the GenerateNativeHeader annotation. For hotspot,
all necessary changes have been pushed into hotspot-rt. For jdk,
there are two webrevs, one with everything and one with just the
category 1 changes, to make it easier to see them. Finally for the
root repository there are only new files in the common subdir.<br>
><br>
> root, configure script and makefiles:<br>
> <a moz-do-not-send="true"
href="http://cr.openjdk.java.net/%7Eerikj/build-infra-m1/webrev-root-new/">http://cr.openjdk.java.net/~erikj/build-infra-m1/webrev-root-new/</a><br>
><br>
> langtools, 1 new makefile:<br>
> <a moz-do-not-send="true"
href="http://cr.openjdk.java.net/%7Eerikj/build-infra-m1/webrev-langtools-new/">http://cr.openjdk.java.net/~erikj/build-infra-m1/webrev-langtools-new/</a><br>
><br>
> langtools, GenerateNativeHeader annotation (this is already
going in through tools, but adding it here for reference as the
jdk changes depend on it)<br>
> <a moz-do-not-send="true"
href="http://cr.openjdk.java.net/%7Eerikj/build-infra-m1/webrev-langtools-nativeheader/">http://cr.openjdk.java.net/~erikj/build-infra-m1/webrev-langtools-nativeheader/</a><br>
><br>
> corba, 1 new makefile:<br>
> <a moz-do-not-send="true"
href="http://cr.openjdk.java.net/%7Eerikj/build-infra-m1/webrev-corba-new/">http://cr.openjdk.java.net/~erikj/build-infra-m1/webrev-corba-new/</a><br>
><br>
> jaxp, 1 new makefile<br>
> <a moz-do-not-send="true"
href="http://cr.openjdk.java.net/%7Eerikj/build-infra-m1/webrev-jaxp-new/">http://cr.openjdk.java.net/~erikj/build-infra-m1/webrev-jaxp-new/</a><br>
><br>
> jaxws, 1 new makefile<br>
> <a moz-do-not-send="true"
href="http://cr.openjdk.java.net/%7Eerikj/build-infra-m1/webrev-jaxws-new/">http://cr.openjdk.java.net/~erikj/build-infra-m1/webrev-jaxws-new/</a><br>
><br>
> jdk, just the changes to old files<br>
> <a moz-do-not-send="true"
href="http://cr.openjdk.java.net/%7Eerikj/build-infra-m1/webrev-jdk-other/">http://cr.openjdk.java.net/~erikj/build-infra-m1/webrev-jdk-other/</a><br>
><br>
> jdk, all changes including a partial copy of the old
makefiles.<br>
> <a moz-do-not-send="true"
href="http://cr.openjdk.java.net/%7Eerikj/build-infra-m1/webrev-jdk-new/">http://cr.openjdk.java.net/~erikj/build-infra-m1/webrev-jdk-new/</a><br>
><br>
> Of course, if you prefer you can look at the new makefiles
directly in the build-infra/jdk8 repository forest too.<br>
><br>
> These changes should not affect the old build at all. To
build using the new build system, change directory to
"common/makefiles" and:<br>
><br>
> ../autoconf/configure<br>
> make<br>
> (make images)<br>
><br>
> State of the new build (the old build should of course be
unaffected):<br>
><br>
> Linux 32bit: Works<br>
> Linux 64bit: Works<br>
> Windows 32bit: Works<br>
> Windows 64bit: Works<br>
> Solaris i586: Builds but launchers currently unusable<br>
><br>
> Some notes:<br>
><br>
> The old and new build (on linux x64) produce very close to
equal results. There is a comparison script in
common/bin/compareimage.sh with which this can be checked.<br>
> Not all makefiles in jdk have been converted yet, for those
that haven't been, a copy of the old files are used.<br>
> Not all promised features in the java compilation are active
and ready in this milestone. Most notably, it's still not using
more than one cpu and the nifty new dependency tracking is
disabled. A clean build is still pretty fast, but incremental
builds aren't as good as they will be yet.<br>
> On windows, only cygwin is currently supported.<br>
><br>
> Now please share your feedback!<br>
><br>
> /Erik<br>
><br>
> [1] <a moz-do-not-send="true"
href="http://mail.openjdk.java.net/pipermail/build-infra-dev/2012-March/000571.html">http://mail.openjdk.java.net/pipermail/build-infra-dev/2012-March/000571.html</a><br>
><br>
><br>
>
</blockquote>
<br>
</body>
</html>