On Mon, 26 Jul 2004, Mark Taylor wrote:
> 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.
Hopefully not all the changes. You'll see that I switched to linking
against the actual startcl libraries rather than the .o files. Couldn't
understand why they exist when startcl goes to the effort of making
libraries for exactly this purpose.
> 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.
>
So ccdpack uses private tcl include files as well as private itcl include
files??? :-)
Also, just out of curiosity, can you explain why all of the tcl/tk support
tcl scripts are copied from the installed location to the build location?
It seems that what's really happening is that ccdpack is creating an
entirely new tcl/tk binary with an entire set of support libraries;
presumably so that the directory can be moved around? Surely the support
scripts will still be picked up from the standard location after the new
binary is built?
Since the standard tcl/tk now install these into share/tcl8.3/ and not
lib/tcl8.2 that might account for one difficulty in the ccdpack build
system.
> 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.
>
As I said, can you leave in some of the tidy up we did?
And also not have the hard-wired version number of TCL in the Makefile.am?
PS I've committed some .cvsignore files
--
Tim Jenness
JAC software
http://www.jach.hawaii.edu/~timj
|