[Ves] CMakeList VES Help

[Pat Marion]

Hi Thiago,

VES uses a "superbuild", which means several projects in addition to VES
are configured and compiled and placed in the build directory.  The
workspace for the superbuild is in a directory called "CMakeExternals".
After you have run the superbuild, you will find CMakeExternals in your
build directory, and you will find the VES build directory in
CMakeExternals/Build/ves.

Ariel-

You can move projects in the App/ directory to any location and build them,
but you will need to fix paths.  Were you trying to relocate an Android
project or iOS file?  For the iOS project, you will find a .xcconfig file
that you must modify to define the path to the VES source and build dirs.
For Android, you should modify the tools.sh file to update the paths of
source_dir and cmakeexternals_dir.



Here's more general instructions:


To configure and build VES (using /workspace as a root dir):

cd /workspace
git clone git://vtk.org/VES.git
mkdir ves-build
cd ves-build
cmake -DVES_IOS_SUPERBUILD:BOOL=ON -DVES_ANDROID_SUPERBUILD:BOOL=ON ../VES
make -j4


To write a CMakeLists.txt in a new project that uses VES:

# CMakeLists.txt
find_package(VTK REQUIRED)
include(${VTK_USE_FILE})

find_package(VES REQUIRED)
include_directories(${VES_INCLUDE_DIRS})

# now you can link with ${VES_LIBRARIES} and ${VTK_LIBRARIES}



To configure your project:


VTK_DIR=/workspace/ves-build/CMakeExternals/Build/vtk-android
VES_DIR=/workspace/ves-build/CMakeExternals/Build/ves-android
TOOLCHAIN=/workspace/ves/CMake/toolchains/android.toolchain.cmake

cmake -DCMAKE_TOOLCHAIN_FILE=$TOOLCHAIN -DVTK_DIR=$VTK_DIR
-DVES_DIR=$VES_DIR /path/to/myproject


Pat


On Sat, Nov 10, 2012 at 8:04 AM, Aashish Chaudhary <
aashish.chaudhary at kitware.com> wrote:

> I will sen something tomorrow.
>
> Thanks
>
> Sent from my iPhone
>
> On Nov 9, 2012, at 3:32 PM, Ariel Hernán Curiale <curiale at gmail.com>
> wrote:
>
> Hi Thiago,
>
> I tried to move one example from the root of the ves/../App (the kiwi app)
> and I've had too many problems to configure in a proper way the
> CMakeList.txt.
>
> I'm in the same situation like you. If anyone could give us a little
> example and explain how we have to config. the CMakeList.txt to use the VES
> library outside the main folder It would be really grate to me :)
>
>
>      Thanks
> __________________________________
> | Ariel Hernán Curiale Ph.D Student
> | ETSI Telecomunicación
> | Universidad de Valladolid
> | Campus Miguel Delibes
> | 47011 Valladolid, Spain
> | Phone: 983-423000 ext. 5590
> | Web: www.curiale.com.ar
> |_________________________________
>
> El 09/11/2012, a las 19:53, Thiago Tavares Magalhães escribió:
>
> Hallo
>
> First sorry for my bad English.
>
> I started studying the VES recently, but I have done some examples with
> VTK.
> For this, I use CMake. With VTK codes I set the CMakeList normally and run
> the command ccmake to specify, among other things, the directory that is
> the vtk_build.
>
> For VES I do not know which file I must inform the directory within the
> configuration of cmake. In other words, I do not know what the file or
> directory VES equivalent to VTK_build of VTK.
>
> I need to know that. If possible, please also a basic example of a valid
> CMakeList VTK and VES and manages the application to be opened in
> IPadSimulator (or similar).
>
> Many thanks to all!
>
> --
> Thiago Tavares Magalhães <http://lattes.cnpq.br/1989532473555107>
> Instituto Superior de Tecnologia em Ciências da Computação de Petrópolis -
> *FAETERJ*
> Laboratório Nacional de Computação Científica -* LNCC*
>
> _______________________________________________
> Ves mailing list
> Ves at public.kitware.com
> http://public.kitware.com/cgi-bin/mailman/listinfo/ves
>
>
> _______________________________________________
> Ves mailing list
> Ves at public.kitware.com
> http://public.kitware.com/cgi-bin/mailman/listinfo/ves
>
>
> _______________________________________________
> Ves mailing list
> Ves at public.kitware.com
> http://public.kitware.com/cgi-bin/mailman/listinfo/ves
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/ves/attachments/20121110/04132cca/attachment-0001.html>