Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
P
Plumed AlphaFold
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Locked files
Deploy
Releases
Package Registry
Model registry
Operate
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Martin Kurečka
Plumed AlphaFold
Commits
4900be52
There was an error fetching the commit references. Please try again later.
Commit
4900be52
authored
11 years ago
by
Giovanni Bussi
Browse files
Options
Downloads
Patches
Plain Diff
Improved doc
parent
8185d920
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
user-doc/Installation.txt
+31
-23
31 additions, 23 deletions
user-doc/Installation.txt
with
31 additions
and
23 deletions
user-doc/Installation.txt
+
31
−
23
View file @
4900be52
...
...
@@ -18,22 +18,34 @@ the proper arguments on the command line) and we encourage this.
In case you have problems on your architecture, please
report to the mailing list.
You can provide hints to the configure script. In particular,
you can state which compiler you wish to use, e.g. to use Intel compilers:
Useful command line options for ./configure can be found typing
\verbatim
> ./configure
CXX=icpc CC=icc
> ./configure
--help
\endverbatim
You can also tune the compilation options
Notice that some functionalities of PLUMED depend on external
libraries which are looked for by configure. You can typically
avoid looking for a library using the "disable" syntax, e.g.
\verbatim
> ./configure
CXXFLAGS=-O3
> ./configure
--disable-mpi --disable-matheval
\endverbatim
In case you want an MPI build, just use the proper name of the MPI compiler.
Notice that when mpi search is enabled (by default) compilers
such as "mpic++" and "mpicxx" are searched first. On the other hand,
if mpi search is disabled ("./configure --disable-mpi") non-mpi
compilers are searched.
You can better control which compiler is used with the
variables CXX and CC. E.g., to use Intel compilers:
\verbatim
> ./configure CXX=mpic++ CC=mpicc
> ./configure CXX=icpc CC=icc
\endverbatim
Notice that in this example, since icpc is not an mpi compiler, mpi will not
be enabled.
You can also tune the compilation options
\verbatim
> ./configure CXXFLAGS=-O3
\endverbatim
The configure will figure out that MPI library is available and instruct PLUMED
to use it.
In case you want to build with debug flags so as to do some checking you can use
\verbatim
...
...
@@ -41,10 +53,6 @@ In case you want to build with debug flags so as to do some checking you can use
\endverbatim
This will perform some extra check during execution (possibly slowing down PLUMED a bit)
and write full symbol table in the executable.
Other useful command line options for ./configure can be found typing
\verbatim
> ./configure --help
\endverbatim
The main goal of the automatic configure is to find libraries.
In case they are stored in unconventional places you might have to
...
...
@@ -73,6 +81,7 @@ you can just make them available to configure with
\endverbatim
The script is also finding out if function names have the final underscore added,
so this should be completely transparent to the user.
In case blas or lapack are not found, the internal versions are used.
As a final resort, you may also edit the resulting Makefile.conf file.
Notable variables there:
...
...
@@ -155,12 +164,16 @@ This is currently the only way to use a PLUMED static executable on Windows.
We tried to keep PLUMED as independent as possible from external libraries.
Moreover, some libraries (e.g. Almost and Matheval) providing
extra features are optional. However, to have a properly working PLUMED
you need to link BLAS and LAPACK libraries.
In case you cannot install proper BLAS and LAPACK libraries on your machine,
you have the possibility of using an internally compiled (possibly slower) versionx .
Here you find some note.
you need BLAS and LAPACK libraries.
In case you cannot manage to install blas and lapack, you can use the internal
ones. Just add to the CPPFLAGS the flags -D__PLUMED_INTERNAL_BLAS
-D__PLUMED_INTERNAL_LAPACK.
The automatic configure should be able to choose automatically the internal
libraries when necessary.
First of all, the DYNAMIC_LIB variable in the configuration file
Some additional notes follow.
First of all, the DYNAMIC_LIB variable in the Makefile.conf
should contain the flag necessary to load these libraries
(typically -llapack -lblas, but full path specification with -L
should be necessary depending on your system configuration).
...
...
@@ -176,11 +189,6 @@ in configuration file).
is written in C++ and often C++ linkers do not include by default Fortran libraries
which are required for lapack and blas to work. Please check the documentation of your compiler.
In case you cannot manage to install blas and lapack, you can use the internal
ones. Just add to the CPPFLAGS the flags -D__PLUMED_INTERNAL_BLAS
-D__PLUMED_INTERNAL_LAPACK
\section Installing Installing PLUMED
It might be convenient to install PLUMED in a predefined location.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment