User Tools

Site Tools


dev:makefile

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
dev:makefile [2014/03/14 12:32] vondeledev:makefile [2026/01/08 13:28] (current) – removed oschuett
Line 1: Line 1:
-====== Makefile ====== 
- 
-The CP2K Makefile automatically adopts to changes of the code base. 
- 
-To add a file to the source tree, just create it. The Makefile will automatically discover it, compile it, and link it. Consequently, files that do not belong into the CP2K libraries must end on an ignored suffix. 
- 
-The file discovery is based on a simple suffix naming convention: 
-  * **.F files** are Fortran files. They are compiled into an object. They should contain either a ''MODULE'' or a ''PROGRAM''. 
-  * **.f90 files** are included Fortran files. They are **not** compiled into an object. 
-  * **.c files** are C-files. They are compiled into an object. 
-  * **.cu files** are Cuda-C-files. They are compiled into an object using Nvidia's ''nvcc'' 
-  * **.h files** are C-header files. They are included by .c or .cu files. They are **not** compiled into an object. 
- 
-===== 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: 
-<code python> 
-{ 
-"description": "Smart process pinning", 
-"requires": ("../common", "../dbcsr", "../machine", ) 
-} 
-</code> 
- 
-The entry ''requires''  list all the directories on which the code in the current directory may depend upon. This means, modules in the current directory may only use modules from the listed directories. The requirements between directories must **not** have cycles. The dependency generation will check these dependencies. 
- 
-===== Compiling Multiple Versions ===== 
- 
-The Makefile allows to compile multiple versions of all build targets in parallel: 
-<code> 
-$ make ARCH=Linux-x86-64-gfortran VERSION="sopt sdbg popt pdbg" 
-</code> 
-building only the main CP2K binary can be done as  
-<code> 
-$ make ARCH=Linux-x86-64-gfortran VERSION="sopt sdbg popt pdbg" cp2k 
-</code> 
  
dev/makefile.1394800346.txt.gz · Last modified: (external edit)