![]() ![]() Pytest-xdist (for installed testing many tests at once) The links for appropriate enabling arguments to cmake. Select which, if any, you want, and examine Sub-items below are the respective additionalĭependencies of the add-on. What are the add-on capabilities for Psi4 and what are their dependencies ¶Įach of the items below is an independent additional capability that canīe built with P SI4. Perl for testing (April 2022 dropped by v1.6) MPFR (Mar 2022 dropped by v1.6) no longer needed to compile against Libint2 Psutil (transitive dependency of QCEngine) Py-cpuinfo (provides import cpuinfo) (transitive dependency of QCEngine) SciPy (avoidable if necessary by following directions in runtime error message) Pydantic (transitive dependency of QCElemental) Pint (transitive dependency of QCElemental) Networkx (transitive dependency of QCElemental optional for QCElemental but required for P SI4) Msgpack-python for MessagePack (transitive dependency of QCElemental optional for QCElemental but required for P SI4) Optking - (runtime dependency, required at build-time)Īdditionally, there are runtime-only dependencies: Libint - (Libint2 as of Nov 2020 added by v1.4) The following are also required for P SI4, but if not detected, theīuild system will automatically download and build. System utilities: GNU make and GNU install or Ninja, POSIX threads (Pthreads) library Optimized BLAS and LAPACK libraries (preferably NOT one supplied by a standard That software for P SI4 and any notes and warnings pertaining to it. The links below give examples of how to configure Libint, and even C++ compilers on Linux and Mac) can be Practically everything (including Python, CMake, NumPy, BLAS/LAPACK, ![]() The core P SI4 build requires the software below. What are the tools and dependencies strictly required for building Psi4 ¶ How to run Psi4 as Python module after compilation How to run Psi4 as executable after compilation To run P SI4 after installation, you need to configure a few variables: This section outlines the main steps of configuring, compiling, and How to build and install Psi4, the compact version ¶ Options are not to your taste, use the links within coreĭependencies and add-on dependencies to plan a set of arguments to cmake tailored toĭetailed build. ![]() Should this happy scenario not come to pass, or if the default build Make or Ninja in the new build directory. B objdir without any further arguments, and it will invoke cmake,ĭetect some appropriate defaults, configure the build, create a buildĭirectory objdir, and complete, leaving you to only invoke So it’s very possible thatįrom top-level-psi4-dir source directory, you can call cmake -S. An abbreviated build guide can be foundĬMake does a good job scanning your computer to locate libraries, headerįiles, and executables needed for compilation. Planning: how to configure Psi4 and invoke CMake ¶ Performance-tuned, and available for all common operating systems, For pre-built binaries again well-tested, ![]() For a specific, well-tested,Īnd performance-tuned build path, see /installs/latest Sysadmins) are expected to read this file as it is a broad guide to the This section fulfills the duty of every Linux project to have an INSTALLįile detailing how to build it from source. ![]()
0 Comments
Leave a Reply. |