ICODE-ADC/lammps
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

small clarifications and corrections. Sync with current state of affairs

Browse Source
This commit is contained in:
Axel Kohlmeyer
2025-05-19 11:31:42 -04:00
parent a821654ef5
commit b9b59bd23c
2 changed files with 20 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
doc/src/Intro_authors.rst
View File

@ -84,8 +84,9 @@ lammps.org". General questions about LAMMPS should be posted in the
\normalsize \normalsize
Past developers include Paul Crozier and Mark Stevens, both at SNL, Past core developers include Paul Crozier and Mark Stevens, both at SNL,
and Ray Shan, now at Materials Design. and Ray Shan while at SNL and later at Materials Design, now at Thermo
Fisher Scientific.
---------- ----------

25
doc/src/Intro_portability.rst
View File

@ -28,8 +28,9 @@ Build systems
LAMMPS can be compiled from source code using a (traditional) build LAMMPS can be compiled from source code using a (traditional) build
system based on shell scripts, a few shell utilities (grep, sed, cat, system based on shell scripts, a few shell utilities (grep, sed, cat,
tr) and the GNU make program. This requires running within a Bourne tr) and the GNU make program. This requires running within a Bourne
shell (``/bin/sh``). Alternatively, a build system with different back shell (``/bin/sh`` or ``/bin/bash``). Alternatively, a build system
ends can be created using CMake. CMake must be at least version 3.16. with different back ends can be created using CMake. CMake must be
at least version 3.16.
Operating systems Operating systems
^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^
@ -40,11 +41,18 @@ Also, compilation and correct execution on macOS and Windows (using
Microsoft Visual C++) is checked automatically for the largest part of Microsoft Visual C++) is checked automatically for the largest part of
the source code. Some (optional) features are not compatible with all the source code. Some (optional) features are not compatible with all
operating systems, either through limitations of the corresponding operating systems, either through limitations of the corresponding
LAMMPS source code or through incompatibilities of source code or LAMMPS source code or through incompatibilities or build system
build system of required external libraries or packages. limitations of required external libraries or packages.
Executables for Windows may be created natively using either Cygwin or Executables for Windows may be created either natively using Cygwin,
Visual Studio or with a Linux to Windows MinGW cross-compiler. MinGW, Intel, Clang, or Microsoft Visual C++ compilers, or with a Linux
to Windows MinGW cross-compiler. Native compilation is supported using
Microsoft Visual Studio or a terminal window (using the CMake build
system).
Executables for macOS may be created either using Xcode or GNU compilers
installed with Homebrew. In the latter case, building of LAMMPS through
Homebrew instead of a manual compile is also possible.
Additionally, FreeBSD and Solaris have been tested successfully to Additionally, FreeBSD and Solaris have been tested successfully to
run LAMMPS and produce results consistent with those on Linux. run LAMMPS and produce results consistent with those on Linux.
@ -61,8 +69,9 @@ CPU architectures
^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^
The primary CPU architecture for running LAMMPS is 64-bit x86, but also The primary CPU architecture for running LAMMPS is 64-bit x86, but also
32-bit x86, and 64-bit ARM and PowerPC (64-bit, Little Endian) are 64-bit ARM and PowerPC (64-bit, Little Endian) are currently regularly
regularly tested. tested. Further architectures are tested by Linux distributions that
bundle LAMMPS.
Portability compliance Portability compliance
^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^