![]() If these packages are not needed, or already present, set the download variable to no in the setup script. The script can download the main packages needed by the code to run properly. The script can be edited run multiple times, so that steps finished in prior runs do not need to be executed again if they succeeded.on subsequent runs, libraries are downloaded and built, and code_saturne is configured or built, based on the setup configuration. ![]() The setup file should be checked and modified according to need.on the first run, the script attemts to detect some tools, and generates a first setup configuration file.Install_saturne.py works in 2 or more passes. This script is given in the hope that they it will useful, but is simply a wrapper to the actual build system. In case of problems, switching to a regular install is recommended. In most cases, it will be sufficient to obtain a usable build. The install_saturne.py Python script present in the root directory of the code_saturne source tree allows for semi-automatic installation of code_saturne elements and some associated optional libraries. Installing code_saturne does not require root privileges if done correctly. In all other cases, it is strongly recommended to choose an installation path in a user or project directory. In this case, choose a consistent naming scheme, using an additional level of sub-directories, for example:Īlso, as installing to a default system directory requires administrator-level write permissions, and is not well adapted to multiple builds, this should be reserved for Linux package maintainers. This also allows multiple builds, for example, building both an optimized and a debugging version. It is strongly recommended to build the code in a separate directory from the source (the semi-automatic installer enforces this). Any directory structure may be chosen, as long as it is easily comprehensible. In the following sections, we will assume a dedicated directory structure is used, for example: /home/user/code_Saturne/src for source trees, /home/user/code_Saturne/src/build for build trees, and /home/user/code_Saturne/arch for installation (so as to keep directories both separate and easy to locate relative to each other). If unspecified, it will usually be /usr/local or usr. The install directory is the directry where the usable code will be installed.The build directory is the directory in which the configuration and compilation will take place.The source directory is the directory in which the source tree is cloned or unpacked.3 types of directories are considered when installing the code:
0 Comments
Leave a Reply. |