| sourcebuild.texi (117395) | sourcebuild.texi (119256) |
|---|---|
| 1@c Copyright (C) 2002 Free Software Foundation, Inc. | 1@c Copyright (C) 2002, 2003 Free Software Foundation, Inc. |
| 2@c This is part of the GCC manual. 3@c For copying conditions, see the file gcc.texi. 4 5@node Source Tree 6@chapter Source Tree Structure and Build System 7 8This chapter describes the structure of the GCC source tree, and how 9GCC is built. The user documentation for building and installing GCC --- 451 unchanged lines hidden (view full) --- 461@file{gcc/doc/sourcebuild.texi}. 462@end itemize 463 464If the front end is added to the official GCC CVS repository, the 465following are also necessary: 466 467@itemize @bullet 468@item | 2@c This is part of the GCC manual. 3@c For copying conditions, see the file gcc.texi. 4 5@node Source Tree 6@chapter Source Tree Structure and Build System 7 8This chapter describes the structure of the GCC source tree, and how 9GCC is built. The user documentation for building and installing GCC --- 451 unchanged lines hidden (view full) --- 461@file{gcc/doc/sourcebuild.texi}. 462@end itemize 463 464If the front end is added to the official GCC CVS repository, the 465following are also necessary: 466 467@itemize @bullet 468@item |
| 469At least one GNATS category for bugs in that front end and runtime | 469At least one Bugzilla component for bugs in that front end and runtime |
| 470libraries. This category needs to be mentioned in | 470libraries. This category needs to be mentioned in |
| 471@file{gcc/gccbug.in}, and in @file{gnats.html} on the GCC web site, as 472well as being added to the GNATS database. | 471@file{gcc/gccbug.in}, as well as being added to the Bugzilla database. |
| 473@item 474Normally, one or more maintainers of that front end listed in 475@file{MAINTAINERS}. 476@item 477Mentions on the GCC web site in @file{index.html} and 478@file{frontends.html}, with any relevant links on 479@file{readings.html}. (Front ends that are not an official part of 480GCC may also be listed on @file{frontends.html}, with relevant links.) --- 445 unchanged lines hidden (view full) --- 926@end table 927 928FIXME: merge in @file{testsuite/README.gcc} and discuss the format of 929test cases and magic comments more. 930 931@node libgcj Tests 932@subsection The Java library test suites. 933 | 472@item 473Normally, one or more maintainers of that front end listed in 474@file{MAINTAINERS}. 475@item 476Mentions on the GCC web site in @file{index.html} and 477@file{frontends.html}, with any relevant links on 478@file{readings.html}. (Front ends that are not an official part of 479GCC may also be listed on @file{frontends.html}, with relevant links.) --- 445 unchanged lines hidden (view full) --- 925@end table 926 927FIXME: merge in @file{testsuite/README.gcc} and discuss the format of 928test cases and magic comments more. 929 930@node libgcj Tests 931@subsection The Java library test suites. 932 |
| 934Runtime tests are executed via @samp{make check} from the @samp{testsuite} 935directory of the libjava hierarchy in the build tree. Additional runtime 936tests can be checked into this testsuite. | 933Runtime tests are executed via @samp{make check} in the 934@file{@var{target}/libjava/testsuite} directory in the build 935tree. Additional runtime tests can be checked into this testsuite. |
| 937 938Regression testing of the core packages in libgcj is also covered by the 939Mauve test suite. The @uref{http://sources.redhat.com/mauve/,,Mauve Project} 940develops tests for the Java Class Libraries. These tests are run as part 941of libgcj testing by placing the Mauve tree within the libjava testsuite 942sources at @file{libjava/testsuite/libjava.mauve/mauve}, or by specifying 943the location of that tree when invoking @samp{make}, as in 944@samp{make MAUVEDIR=~/mauve check}. --- 201 unchanged lines hidden --- | 936 937Regression testing of the core packages in libgcj is also covered by the 938Mauve test suite. The @uref{http://sources.redhat.com/mauve/,,Mauve Project} 939develops tests for the Java Class Libraries. These tests are run as part 940of libgcj testing by placing the Mauve tree within the libjava testsuite 941sources at @file{libjava/testsuite/libjava.mauve/mauve}, or by specifying 942the location of that tree when invoking @samp{make}, as in 943@samp{make MAUVEDIR=~/mauve check}. --- 201 unchanged lines hidden --- |