You can build a specific test by using the target name for the test executable. Where $ is the name of the component you wish to build. If you wish to build only the library (without tests) then you can type Make Parallel # builds the Parallel test pack Make Weekly # builds the Weekly test pack Make Nightly # builds the Nightly test pack Make Continuous # builds the Continuous test pack If you wish to build a specific test pack then just type make and then the name of the test pack, for example: Make cell_based crypt # builds the cell_based and crypt libraries and all their dependencies Make heart # builds the heart library and all dependencies Make pde # builds the pde library and all dependencies Make ode # builds the ode library and all dependencies Make mesh # builds the mesh library and all dependencies Make linalg # builds the linalg (linear algebra) library and all dependencies Make io # builds the io library and all dependencies Make global # builds the global library and all dependencies You can specify building a specific component library and all its tests by giving make the name of the component target. global, pde, heart etc) is compiled into a library, with a target name given by the name of the component (so the target name for global is global) These targets can be libraries or executables (i.e. ![]() The configure step generates a number of targets which can be built. See below for a complete list of the configuration optionsįor Makefile generators (this is the default) the configure step will generate a bunch of Makefiles, so you just need to run (Windows only) Note that using this CMake option overwrites any specified library locations ![]() You can specify a Boost directory by using the BOOST_ROOT CMake variable (note: NOT an environment variable) eg.Ĭmake -DVTK_DIR=/path/to/vtk /path/to/source You can specify a VTK directory by using the VTK_DIR CMake variable (note: NOT an environment variable). You can specify a HDF5 folder by setting the HDF5_ROOT environment variables. You can specify a Sundials folder by setting the SUNDIALS_ROOT environment variables. PETSC_DIR=/path/to/petsc PETSC_ARCH=linux-intel cmake /path/to/source You can specify a PETSc folder and Arch by setting the PETSC_DIR and PETSC_ARCH environment variables. You can specify a C++ compiler by setting the CXX environment variable. You need -DHAVE_PARMETIS=ON to skip the step which checks that Parmetis is working, it works for the main Chaste build, so not to worry (for now). Note you need the -DChaste_USE_PETSC_HDF5=OFF because I'm using "Petsc for Windows" for Petsc, which doesn't include hdf5 libraries. So on scratch the command isĬmake -DCHASTE_DEPS_ROOT_DIR=D:\chaste_windows\build\install\third_party_libs -DChaste_USE_PETSC_HDF5=OFF -DHAVE_PARMETIS=ON -GVisual Studio 10 Win64 \path\to\source This should work on (at least) Ubuntu with all required dependencies installedįor windows (on scratch at least) you need to specify a generator (using -G) and the location of the third party libraries (using -DCHASTE_DEPS_ROOT_DIR=). Look under the Testing Step heading below for more information To run the tests you can either call make on the test target This will compile the Chaste libraries and all the tests. The standard way (for Makefile generators) to compile the Chaste project using CMake is to make a build directory, call cmake on the root of the source tree and then use make to compile. from trying to build using the root directory of the source tree). The Chaste CMake system will prevent you from doing in-source builds (i.e. It is standard for CMake to build your project in a separate (empty) directory to your source tree (This can still be in a subdirectory within the source tree). Other Generators include one for Microsoft Visual C++, which outputs MSVC project files during the configure step. By default this is a Makefile generator, so the configure step will output a bunch of Makefiles, with which you can build you project. ![]() During this step you can specify a Generator. In the first you call cmake to configure your project. The remainder in /cmake/ are left over from the old CMake setup for windows (some are still in use)ĬMake is a build system generator, so splits up the build process into two steps. Most of these are kept in /cmake/Modules, and there is a base CMake Configure script for Chaste in /cmake/Config/. All the cmake macros and finder scripts (apart from those in the main CMake distribution) are in /cmake/. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |