Skip to content

Commit 1b14790

Browse files
committed
compile docs
1 parent 11ad675 commit 1b14790

File tree

2 files changed

+6
-5
lines changed

2 files changed

+6
-5
lines changed

source/user/guides/compile.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ To compile Xara from source, follow these steps:
3737

3838
.. code-block:: bash
3939
40-
conda install -c conda-forge cmake ninja ifx_win-64 mkl-devel conda-forge/label/mkl_rc::blas
40+
conda install -c conda-forge cmake ninja ifx_win-64 mkl-devel conda-forge/label/mkl_rc::blas tk
4141
4242
.. note::
4343

source/user/guides/develop.rst

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ The following steps only need to be performed once to set up the development env
5353

5454
.. code-block:: bash
5555
56-
conda install -c conda-forge cmake ninja ifx_win-64 mkl-devel conda-forge/label/mkl_rc::blas
56+
conda install -c conda-forge cmake ninja ifx_win-64 mkl-devel conda-forge/label/mkl_rc::blas tk
5757
5858
5959
4. Create a *persistent* build tree for C/C++ development:
@@ -82,9 +82,10 @@ The following steps only need to be performed once to set up the development env
8282
c. When ``libOpenSeesRT.so`` is built in a persistent tree, the ``xara``
8383
package needs to be told where to find it. This is done by setting
8484
an environment variable with the name ``OPENSEESRT_LIB`` to point to
85-
the location of ``libOpenSeesRT.so`` in the build tree.
86-
You may want to add a line like the following to your shell
87-
startup script (e.g., ``.bashrc``):
85+
the location of ``libOpenSeesRT.so`` (on Windows the equivalent file is ``libOpenSeesRT.dll``) in the build tree.
86+
To do this, run the following command from your shell, replacing
87+
``/path/to/libOpenSeesRT.so`` with the actual path to the file and
88+
``my_environment`` with the name of your Anaconda environment:
8889

8990
.. code-block:: bash
9091

0 commit comments

Comments
 (0)