You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+31Lines changed: 31 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,6 +27,37 @@ Pre-made grids for use in MUSICA are available [here](https://wiki.ucar.edu/disp
27
27
Checkout our [software development plan](docs/Software%20Development%20Plan.pdf)
28
28
to see how you can contribute new science to MUSICA software.
29
29
30
+
## Developer Options
31
+
32
+
### Specifying dependency versions via paramaterization at configure time
33
+
34
+
Introduced in [Pull Request #124](https://github.com/NCAR/musica/pull/124), it is possible for developers to specify which versions of various dependencies should be used. These options are currently limited to those dependencies managed via `FetchContent`. This change allows for more easily testing `musica` against changes committed in different repositories and branches. The environmental variables introduced are outlined in the following table.
35
+
36
+
#### CMake Dependency Variables
37
+
38
+
| Musica Dependency | Repository | Branch, Tag or Hash|
0 commit comments