Hi Andrew,
On 2010-05-17 10:09, Andrew Ross wrote: > On Mon, May 17, 2010 at 09:27:06AM +0200, Arjen Markus wrote: >> Hello, >> >> I am chiming in very late in this discussion (we had a very long weekend >> off in my little country at the sea and I did not feel very motivated >> to read my e-mail for a variety of reasons), but my idea is this: >> Rather than let CMake find out everything it needs to about what >> version of Tcl to use, why not let a small Tcl script do the job? >> Tcl offers enough introspection to make that happen. >> >> Here is a sketch: >> - The current FindTcl.cmake file is fine, as far as looking for tclsh >> is concerned (possibly modulo a specific tclsh that you want used). >> - It can then start that particular tclsh with a script that will >> report what libraries that tclsh shell uses >> >> (I have something of that kind already, though it will need to be >> adapted for this purpose) > > Yes! In my opinion this is exactly what cmake should do. The user only > has to ensure that the correct tclsh is in the path and then everything > else is automatically found. With this is should be impossible to > get the wrong versions of libraries or headers. Why this wasn't done > in the first place I don't know. > > The only down side of relying on actually running an executable is > that it doesn't work for cross-compilation, but in this case you expect > to have to do a bit more work. Perhaps using the current approach as a > fall-back is the way to go? > I am willing to investigate this option including the fall-back. Regards, Arjen ------------------------------------------------------------------------------ _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
