Whichever type of component you have added, the final step,
after committing your changes, is to ensure that your new
component and its
newly-declared dependencies are integrated into the network
of dependencies contained within the
Makefile.dependencies
file at the top level. To do this, you must go to the top
level of a full checkout of the repository, make
sure your new component is checked out there, then delete
Makefile.dependencies and remake it.
The% rm Makefile.dependencies % make Makefile.dependencies # ... remakes componentset.xml, and from that Makefile.dependencies % cvs -n update M componentset.xml M Makefile.dependencies
Makefile.dependencies file is generated
using a Java program, so you must have a JDK in your
path before starting this procedure
(you might possibly need to run ./configure
--no-recursion to bring the Makefile
there up to date with respect to Makefile.in).
Alternatively, you can invoke make with
make JAVA=/path/to/jdk Makefile.dependencies.Double-check both Makefile.dependencies and
componentset.xml, using cvs diff
<file>: ensure that the right material has
been added before re-committing these two files. If this
diffing appears to indicate that material has been
removed from either file, this probably means that
you don't have a full or up-to-date checkout, so investigate
that and fix things up before committing.
If the component you have added should be included in the
`make world' build, then you should add it to the list of
targets listed in the ALL_TARGETS variable at
the top of the top-level Makefile.in. You
should do this only if both this component and anything
it depends upon build successfully from scratch.