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
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,7 +55,8 @@ pip install -e .
55
55
#### Optional Spack environment variations
56
56
The Spack environment used to build Quandary is defined in `.spack_env/spack.yaml`.
57
57
You can add or remove packages from the `specs` list as needed or use different variants of these.
58
-
For instance, if you want to use the debug variant (which builds Petsc in debug mode) you can use `quandary@develop+test+debug`.
58
+
For instance, if you want to use the debug variant (which builds Quandary and Petsc in debug mode) you can use `quandary@develop+test build_type=Debug`.
59
+
To build with `PetscInt`s set to 64-bit integers, use `quandary+int64`.
59
60
To use a specific version of Petsc instead of the latest release, you can do e.g. `quandary@develop^petsc@3.22.1`.
60
61
The `+test` variant (by default on in `.spack_env/spack.yaml`) adds python and pip to the Spack environment.
61
62
This allows `pip install` to install python packages to your Spack virtual environment rather than a global one.
@@ -89,6 +90,7 @@ cmake ..
89
90
make
90
91
```
91
92
93
+
To build in debug mode use `cmake -DCMAKE_BUILD_TYPE=Debug ..`.
92
94
Add the path to Quandary to your `PATH` variable with `export PATH=/path/to/quandary/:$PATH`, so your binary can be found.
93
95
Alternatively, you can install the Quandary executable in a specific path (such as the default `/usr/local/bin` to have it in your `PATH` automatically):
0 commit comments