dev:packages
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
dev:packages [2014/07/28 09:28] – created oschuett | dev:packages [2020/08/21 10:15] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | + | ====== Packages | |
- | ===== Packages ===== | + | |
The code base is structured into directories. This will allow for making CP2K more modular, i.e. consisting of smaller packages with fewer dependencies. Every directory therefore contains a file named '' | The code base is structured into directories. This will allow for making CP2K more modular, i.e. consisting of smaller packages with fewer dependencies. Every directory therefore contains a file named '' | ||
Line 19: | Line 18: | ||
The optional entry '' | The optional entry '' | ||
+ | |||
+ | ====== Creating New Packages ====== | ||
+ | A very helpful tool for the creation of new packages is the '' | ||
+ | < | ||
+ | cp2k/tools$ ./ | ||
+ | </ | ||
+ | |||
+ | A package-plan describes changes to the current file-layout. It can be used to assign files to new or different packages. And it can be used to change the requirements of packages. The script will outputs the dependency-violations that the changes of a package-plan would create. Hence, it provides a convenient way to analyses module dependencies and to design new packages. | ||
+ | |||
+ | |||
dev/packages.1406539735.txt.gz · Last modified: 2020/08/21 10:14 (external edit)