Download MUS COD II

Transcript
To remove the files of a <build_type> installation, just type
name@machine:~/MUSCOD_SUITE> ./cleanup --btype=<build_type>
Install To System It is possible to install the packages to subfolders of a central location,
from where it can be used by every regular user. The install procedure is identical to the one
described above, except that the installation path prefix (e.g. /use/local) has to be specified:
name@machine:~/MUSCOD_SUITE> ./bootstrap --ipref=<prefix>
Depending on their type, files are installed to different subfolders:
→ <prefix>/bin/: executables
→ <prefix>/lib: static (*.a) and shared (*.so) libraries (on 32 bit platform)
→ <prefix>/lib64: static (*.a) and shared (*.so) libraries (on 64 bit platform)
→ <prefix>/share/<package>/: other data related to <package>
Attention: Applications for MUSCOD-II and MUSCOD-II itself are never installed to a dir
other than ~/MUSCOD_SUITE/Apps/<app>/<build_type>/! After a successful installation, the
suite dir could be removed. But mind the note above and do not delete your applications!
Deinstallation has to be done manually. Installation logs are provided at least by the CMake
packages in their respective binary dirs.
Usage with other Software Suites In case you use other software from the SimOpt
repository which uses common packages (e.g. both MUSCOD-II and VPLAN both use COMMON CODE), it may be advisable to have the common packages installed only once on your
system. This can be achieved by creating a symlink called Packages (with exactly that name!)
in the MUSCOD_SUITE dir to the single common Packages directory before the checkout, e.g.:
user@machine:~/MUSCOD_SUITE> ln -s ../Packages
Then the packages will actually be checked out to the packages directory on the “suites”
level. Using the same technique on your other projects ensures that you only have one actual
location for the sources of common packages. You are expected to encounter problems with
this approach if you try to mix branches/tags/trunk versions of different suites, e.g. a special
MUSCOD-II/tag with MUSCOD-II/trunk. In this case, MUSCOD-II will try to check out a
tagged version of the package and MUSCOD-II will try to check out the trunk version of the
package to the same directory. In this case the use of suite packages is not advisable and you
are encouraged to perform the recursive checkout manually.
Since revision 6, there is only one executable, which links dynamically shared object files at
runtime, corresponding to algorithmic settings.
17