User Tools

Site Tools


dev:packages

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

dev:packages [2014/07/28 09:28]
oschuett created
dev:packages [2014/07/28 10:55] (current)
oschuett
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 ''​PACKAGE''​ . A typical ''​PACKAGE'',​ which uses python syntax, looks like this: 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 ''​PACKAGE''​ . A typical ''​PACKAGE'',​ which uses python syntax, looks like this:
Line 19: Line 18:
  
 The optional entry ''​archive''​ allows to overwrite the filename of the archive, which is created during compilation. The default name is "​libcp2k<​package_name>"​. The optional entry ''​archive''​ allows to overwrite the filename of the archive, which is created during compilation. The default name is "​libcp2k<​package_name>"​.
 +
 +====== Creating New Packages ======
 +A very helpful tool for the creation of new packages is the ''​plan_packages.py''​ script. It takes as argument a package-plan. ​
 +<​code>​
 +cp2k/tools$ ./​plan_packages.py ./​pkg_plan.txt ​
 +</​code>​
 +
 +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.txt · Last modified: 2014/07/28 10:55 by oschuett