On Mon, 26 Jul 2004, Tim Jenness wrote:
> On Mon, 26 Jul 2004, Mark Taylor wrote:
>
> > On Tue, 20 Jul 2004, Tim Jenness wrote:
> >
> > > PS I don't think ccdpack/tasks should have an explicit component.xml
> > > declaring "ccdtasks". It's a subcomponent of ccdpack not an entity in its
> > > own right (and if it is an entity in its own right it should include some
> > > build dependencies.
> >
> > I added component.xml files in all the CCDPACK subdirectories
> > because (AFAIR) starconf or bootstrap or something was complaining
> > that no component.xml{,.in} was present; my understanding was that
> > (though not why) every directory in the tree needed these files.
> > I certainly don't intend for the ccdpack subdirs to be built or
> > installed as separate components, they're just there for tidiness.
> > Norman, is there any reason I can't just remove the
> > component.xml{,.in} files in the ccdpack/* directories?
>
> Yes. starconf complains but the decision was that subdirs of apps should
> not include their own component.xml files since they don't
> make install also distinguishes a directory that contains a component.xml
> from a directory that doesn't - you get a manifest for each component.xml
> present.
I have removed the ccdpack/{main,tasks,help,gen}/component.xml{,.in} files
as suggested. Running ./bootstrap in ccdpack/ now recurses into each
of its subdirectories and in each one says:
Using starconf in /mbt/starauto/buildsupport ...
starconf
starconf-validate: the following files are required but do not exist:
component.xml.in
starconf-validate: the following files should be checked in, but aren't
component.xml.in component.xml
Bootstrap already up to date -- not overwriting
autoreconf --install --symlink
Putting files in AC_CONFIG_AUX_DIR, `../..'.
libtoolize: `config.guess' exists: use `--force' to overwrite
libtoolize: `config.sub' exists: use `--force' to overwrite
libtoolize: `ltmain.sh' exists: use `--force' to overwrite
configure.ac:10: required file `component.xml.in' not found
autoreconf: automake failed with exit status: 1
the result is that ./bootstrap fails to write any configure files
for me. Any idea other than reinstating said files?
Mark
--
Mark Taylor Starlink Programmer Physics, Bristol University, UK
[log in to unmask] +44-117-928-8776 http://www.star.bris.ac.uk/~mbt/
|