On Fri, 17 Oct 2014, Tim Jenness wrote:
> On Fri, Oct 17, 2014 at 2:41 AM, Peter W. Draper <[log in to unmask]>
> wrote:
> On Thu, 16 Oct 2014, Tim Jenness wrote:
>
> Most things now work with some tweaks to skycat and
> blt.
>
>
> I'm surprised you needed so many, in principle all these
> packages should get the X11 setup from tkConfig.sh, so only Tk
> should need hacking, clearly not true in practice.
>
>
> Neither vtk nor cmake seem to use tkConfig.sh. The Starlink configure script
> passes the Tk location into cmake. My problem is that the TK_INCLUDE_PATH
> can't include multiple paths.
>
> and that ctest for X11 passes (as I expected it to). How do I tell the VTK
> Tk code that it also needs X11 then?
Sorry currently no real idea. The CMAKE_INCLUDE_PATH is supposed to a
genuine PATH (colon separated) so that should have worked. Searching the
docs you could try CMAKE_PREFIX_PATH=$STARLINK_DIR alongside all the
Tcl/Tk definitions, but like you I'm grabbing at straws on this one.
|