Or, If you are having trouble with installing things with pip due to disk/folder permissions, try adding -user to the pip flags in order to install modules for the local user. $ python3 -m pip install pybind11 sphinx sphinx-autodoc-typehints NOTE: You can also install pybind11, Sphinx, and related modules directly through pip. Following that, you can install the necessary dependencies by running these commands in a terminal window: $ brew update $ brew install gcc gfortran openjdk doxygen python3 pybind11 sphinx-doc $ python3 -m pip install sphinx-autodoc-typehints The easiest way to satisfy these dependencies on a Mac is to install the Homebrew package manager. Softwareīuild GeoTess and core RSTT libraries and testsīuild documentation for C++, C, and Fortran code The version numbers listed are those used and tested in development. If that fails, they will fall back to searching the path provided in the above variables, if set, in order.īelow is a list of packages and software required to build RSTT from source. In both the Java and Python interfaces, RSTT will first attempt to load the appropriate libraries through the system paths. If you are having difficulty with strange errors related to paths during compilation, try and temporarily remove any remnants of past RSTT versions in environment variables such as $PATH, $LD_LIBRARY_PATH, $DYLD_LIBRARY_PATH, $DYLD_FALLBACK_LIBRARY_PATH, and $SLBM_ROOT or $SLBM_HOME.Īfter compiling, when writing your own codes that utilize the latest RSTT libraries, you may find it useful to set one of the following environmental variables to the root directory of RSTT: During the compilation process, the Makefiles will point to the correct library paths within the default directory structure. In RSTT v3.2.0, no paths should need to be specified in any environment variables to compile and run. This will be addressed in the next release, but in the meantime these errors may be temporarily resolved by adding " -std=c++11" to the CXXFLAGS in each Makefile where it is present. You can use "dot" to generate graphs in your documentation, as described here: įor instructions on actually generating the documentation, see this page: ĭoxygen uses a whole bunch of special tags to parse information.Compiling errors on latest MacOS Changes to GCC on the latest versions of MacOS have resulted in compiling errors on RSTT v3.2.0. One very handy feature of Doxygen is the ability to embed LaTeX formulas into the documentation: These blocks are then parsed, and output can be generated in several different formats (HTML, LaTeX, man pages, etc): The Doxygen manual is exhaustive, and there's no point in reproducing it here.ĭoxygen works by commenting your code using special blocks. This is due to Apple once again putting its head up its own ass by moving away from GCC and toward whatever compiler-of-the-month they think is better. Ran into a slew of difficulties compiling, due to invalid flags and libraries compiled with incompatible compilers. Typically it's located in /usr/local/bin/dot. "dot" should be installed and available on the path, so when you type $ which dot you should see a location returned. This software has a binary installer for common platforms, and is open-source. #!/bin/sh # run configure # make # make installĭoxygen uses "dot", part of Graphviz visualization software, for producing diagrams.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |