It is pre-built library, that is you don't need to compile it. However it is
CMake-aware, therefore you can use it in your program putting
find_library(CMTK) into your CMakeLists.txt.
So to use this in your program you should start writing CMakeLists.txt file
(as described in tutorial). The .cmake
Hello,
I'm a beginner with cmake, and I did not find answers whether in the cmake
documentation or in the archive of the mailing list.
I run a Ubuntu 64 bits and want to use a program.
I've downloaded the .tar.gz file, then extracted it. The structure of the
extracted files is :
usr/local/ -
Hi Jc,
yes, I did. Actually "origin/master" for most of our dartclients.
Thanks,
Sascha
On 03/26/2011 05:43 PM, Jean-Christophe Fillion-Robin wrote:
Hi Sasha,
Out of curiosity, what's the value of PROJ_GIT_BRANCH ?
Did you specify /. For example: "master/origin"
Jc
On Sat, Mar 26, 2011 at
Hi Sasha,
Out of curiosity, what's the value of PROJ_GIT_BRANCH ?
Did you specify /. For example: "master/origin"
Jc
On Sat, Mar 26, 2011 at 11:54 AM, Sascha Zelzer wrote:
> Hi,
>
> we are using the ExternalProject module from CMake 2.8.4 and are observing
> a strange git update problem on Wi
Hi,
we are using the ExternalProject module from CMake 2.8.4 and are
observing a strange git update problem on Windows 7 when running a CTest
script (using the new-style ctest_build, etc. commands).
Our ExternalProject_Add call essentially looks like this:
ExternalProject_Add(${proj}
GIT
2011/3/25 Tyler :
> I just use:
>
> set (CPACK_GENERATOR "ZIP")
>
> and that seems to work.
>
> I think those CPACK_BINARY_* variables you're setting are only
> meaningful in CPack's context, not in CMake's (i.e. those vars are
> what CMake writes out in CPackConfig.cmake for Cpack's later use).
T
