Steve,
On 2004 Dec 6 , at 09.06, Rankin, SE (Stephen) wrote:
> ./applications/datacube/component.xml
> ./applications/pongo/component.xml
> ./applications/echwind/component.xml
These aren't configured because they're not mentioned in the
AC_CONFIG_SUBDIRS macro in ./applications/configure.ac. All three do
have entries in Makefile.dependencies (because the construction of that
scans all the component.xml files in the tree), but nothing depends on
them and they're not mentioned in ./Makefile.in, so they're not built
as part of 'make world'.
Ah! But of course they'll be built by your autobuild process....
Issue 1: is this correct for these three applications? I know that
datacube has a couple of documentation issues, which Tim is patiently
waiting for me to address. I presume echwind is my problem also,
because it has the doleful letters `ech' in it. Pongo I have no clue
about.
I've just tried and, well -- echwind appears to build OK, and I've
added a mention of it to Makefile.in and applications/configure.ac. I
must just have forgotten to add them when I configured echwind.
Issue 2: is this a good thing? Yes -- there has to be a way of having
something in the tree without it being automatically built, perhaps for
the very basic reason that it won't build. This is largely the case
with datacube, although there the problem is a documentation one rather
than that the code doesn't work.
> ./applications/obsolete/chart/component.xml
> ./applications/obsolete/iras90/component.xml
> ./applications/obsolete/ircamdr/component.xml
> ./applications/obsolete/email/component.xml
These aren't being configured for the same reason -- directory
'obsolete/' isn't mentioned in applications/configure.ac. These ones
should obviously never be built by default.
The attached script will find all the components which are to be
configured and echo them on stdout. This way, there is a compatible
mechanism for controlling whether something is included in `make world'
and included in the nightly build. Everything which is configured is
included in the nightly build; everything in ALL_TARGETS is made by
`make world'. The contents of this target is a subset of what's
configured, but will typically imply a larger set via dependencies. If
that larger set is larger than the set of configured files, `make
world' will fail, so that should get fixed fairly promptly.
> ./docs/ssn/078/component.xml
I'm not sure what to do there. Should we have this documentation being
built nightly?
> ./thirdparty/fsf/m4/component.xml
> ./thirdparty/fsf/libtool/component.xml
The thirdparty/fsf directory isn't included in thirdparty/configure.ac
AC_CONFIG_SUBDIRS. The buildsupport tools are configured in special
ways by ./bootstrap so shouldn't be included in this tree-wide
configuration. They wouldn't be picked up by the attached script.
> component.xml for figaro has not been checked in to CVS at all.
Added now.
See you,
Norman
--
----------------------------------------------------------------------
Norman Gray : Physics & Astronomy, Glasgow University, UK
http://www.astro.gla.ac.uk/users/norman/ : www.starlink.ac.uk
|