Norman,
OK, that is fine thanks.
I have another question now. How is the main componentset.xml file
maintained, is it generated automatically by configure and then put into cvs
manually, or is it maintained by hand?
The path to the jpeg lib is wrong in the main componentset.xml in cvs, but
has been fixed in the jpeg source. I have been using componentset.xml to
construct the autobuild.conf configuration file with an xslt style sheet,
which works. But as autobuild then checks out every module individually
using the path defined in componentset.xml, it fails before it even starts
building anything. Once the path is fixed, then the nightly build should be
working. I would fix it but I wasn't sure how componentset.xml was generated
and maintained.
Steve.
-----Original Message-----
From: Starlink development [mailto:[log in to unmask]] On Behalf Of
Norman Gray
Sent: 28 November 2004 20:13
To: [log in to unmask]
Subject: Re: A first look at the nightly build
Steve,
On 2004 Nov 26 , at 16.05, Rankin, SE (Stephen) wrote:
> As you know the build system better than I, do you know if there is a
> test
> that I could perform from a shell script that would verify that the
> buildsupport software had been built? Something like:
The ./bootstrap script, either plain ./bootstrap or else './bootstrap
--buildsupport', should exit with a zero exit status if all goes well.
Let me know if this is not the case.
The manifest files for the bootstrap components will also be installed
only if the installation is successful (this wasn't true before ten
minutes ago (oops), but should be true as of now).
This should mean that
% ./bootstrap && make configure-deps && ./configure -C
--without-stardocs && make world
should do the right thing. Is that what you're thinking of?
See you,
Norman
--
----------------------------------------------------------------------
Norman Gray : Physics & Astronomy, Glasgow University, UK
http://www.astro.gla.ac.uk/users/norman/ : www.starlink.ac.uk
|