Commit a4051249 authored by Harald Scheirich's avatar Harald Scheirich
Browse files

DOC: Add documentation about adding data

parent b1ebeb31
Pipeline #246311 passed with stage
...@@ -119,4 +119,16 @@ Most dependencies in iMSTK are forked. This way we don't depend on the remote re ...@@ -119,4 +119,16 @@ Most dependencies in iMSTK are forked. This way we don't depend on the remote re
- Merge upstream (or rebase): `git merge upstream/<branch to update from>` - Merge upstream (or rebase): `git merge upstream/<branch to update from>`
- Push your changes - Push your changes
After updating your fork you can proceed with the beginning of this guide on how to pull a different source. After updating your fork you can proceed with the beginning of this guide on how to pull a different source.
\ No newline at end of file
# Adding data to the data repository
iMSTKs data sits in a separate repository https://gitlab.kitware.com/iMSTK/imstk-data it is downloaded by the superbuild when testing or the examples are enabled, to add a resource to the repository two steps are necessary
## Add Data to repository
The repository is checked out in your build directory as `External\iMSTKData\src`, data can be added to the structure here and directly commited and pushed.
## Update SHA in ExternalData.cmake
The file that controls the downloading of the data is `CMake/External/External_iMSTKData.cmake` after commiting and pushing a change in the iMSTKData repository, the SHA to checkout needs to be updated to the SHA matching your latest commit.
\ No newline at end of file
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment