I tried just listing the single step, and for some reason (probably my
fault) it didn't work.
I did get this working, but I had to add two things to keep tcl and tk
from breaking fixup_bundle -- I had to make the Tcl/Tk SO libraries
writable, and I needed to delete tclsh and wish, because fixup_bu
On Fri, Apr 23, 2010 at 1:11 PM, Luigi Calori wrote:
> There is some info at
> http://www.kitware.com/products/archive/kitware_quarterly1009.pdf
>
> based on that I thought it was enouth do depend upon just the install in
> your case...
>
Luigi is correct: it should be sufficient to list "DEPEND
There is some info at
http://www.kitware.com/products/archive/kitware_quarterly1009.pdf
based on that I thought it was enouth do depend upon just the install in
your case...
I am collecting external projects for several libs, It seem you are
building at least VTK and Tcl and Tk that I lack..
Answering my own question -- I think. This maybe is information that
could be added to the documentation for ExternalProjects.cmake!
ExternalProject_Add creates a project, e.g.
ExternalProject_Add(tcl
CVS_REPOSITORY ":pserver:anonymous:@tcl.cvs.sourceforge.net:/cvsroot/tcl"
CVS_TAG -r core-8-5-7
So... I have been working on my 'Holy Grail' CMakeLists.txt that
builds all prerequisites to my application as ExternalProjects, and
then builds my application (also as an External Project).
In getting it to work on OS X and Linux I ran into an issue:
If you build Tcl, and install it, it installs
