Brad, Tim, anyone:
I've just re-reached the stage of being able to build CCDPACK (why do
I feel like I'm wading through treacle?) hopefully with or without
itcl. In order to do this I've had to, amongst other things, back
out of the changes to configure.ac and Makefile.am that Brad made
17 July to use the STAR_PATH_TCLTK macro.
I haven't investigated exactly what doesn't work right when
STAR_PATH_TCLTK is being used, except that it's probably down to
the idiosyncratic way that CCDPACK assembles the script files it
needs - if I was rewriting it from scratch it would probably do things
in a more standard way, but I'm not.
Although STAR_PATH_TCLTK seems like it ought to be the way forward,
as I've mentioned before, CCDPACK has rather stringent requirements
on the TCL/TK setup it uses (this time not for historical reasons,
it requires some semi-private TCL include files), so in practice
I'm not sure it's worth getting it to look for a non-starlink
version of it, since it probably wouldn't work anyway.
For this reason I'd argue that the apparently retrograde step
of removing STAR_PATH_TCLTK again is a reasonable thing to do.
Sorry to play ping pong, and I'm certainly not trying to discourage
people apart from me from tinkering with CCDPACK, but unless
I get an objection by tomorrow I will restore the CCDPACK
configure.ac and Makefile.am to their pre-STAR_PATH_TCLTK state.
Mark
--
Mark Taylor Starlink Programmer Physics, Bristol University, UK
[log in to unmask] +44-117-928-8776 http://www.star.bris.ac.uk/~mbt/
|