This repository serve as a backup for my Maxwell-TD code
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Qi Jian Lim 6c05defaa1 Fix: add HybridMesher as normal source folder (not submodule) 3 months ago
..
cmake Fix: add HybridMesher as normal source folder (not submodule) 3 months ago
packages Fix: add HybridMesher as normal source folder (not submodule) 3 months ago
sampleScripts Fix: add HybridMesher as normal source folder (not submodule) 3 months ago
.gitignore Fix: add HybridMesher as normal source folder (not submodule) 3 months ago
CMakeLists.txt Fix: add HybridMesher as normal source folder (not submodule) 3 months ago
CTestConfig.cmake Fix: add HybridMesher as normal source folder (not submodule) 3 months ago
Copyright.txt Fix: add HybridMesher as normal source folder (not submodule) 3 months ago
LICENSE Fix: add HybridMesher as normal source folder (not submodule) 3 months ago
PackagesList.cmake Fix: add HybridMesher as normal source folder (not submodule) 3 months ago
ProjectName.cmake Fix: add HybridMesher as normal source folder (not submodule) 3 months ago
README.md Fix: add HybridMesher as normal source folder (not submodule) 3 months ago
TPLsList.cmake Fix: add HybridMesher as normal source folder (not submodule) 3 months ago
Version.cmake Fix: add HybridMesher as normal source folder (not submodule) 3 months ago
project-checkin-test-config.py Fix: add HybridMesher as normal source folder (not submodule) 3 months ago

README.md

TribitsExampleProject Documentation

The project TribitsExampleProject defines a TriBITS CMake project designed to provide a simple example to demonstrate how to use the TriBITS system to create a CMake build, test, and deployment system using a package-based architecture. To build all of the packages from TribitsExampleProject, a Fortran compiler is needed.

To build and test the project, one must first create a build directory and configure by pointing to the TriBITS source dir <tribits-dir> (i.e. TriBITS/tribits) and the TribitsExampleProject project source dir with:

  mkdir <build-dir>
  
  cd <build-dir>
  
  cmake \
    -DTribitsExProj_TRIBITS_DIR=<tribits-dir> \
    -DCMAKE_INSTALL_PREFIX=<TribitsExampleProject-install-dir>
    -DTribitsExProj_ENABLE_TESTS=ON \
    -DTribitsExProj_ENABLE_ALL_PACKAGES=ON
    -DTribitsExProj_ENABLE_SECONDARY_TESTED_CODE=ON \
    -DCMAKE_CXX_COMPILER=g++ \
    <path-to-TribitsExampleProject>

then build and test with:

  make -j4 && ctest -j4

and then install:

  make install

TribitsExampleProject will be installed to <TribitsExampleProject-install-dir> and this path should be then used to point -DCMAKE_PREFIX_PATH=<TribitsExampleProject-install-dir> when building e.g. TribitsExampleApp

The layout of a TriBITS project is described in:

Otherwise, this example TriBITS project is simple enough that it should be enough to get started as a template.