Tips for ABINIT users and developers

User Tools

Site Tools

Trace:
build:feature_triggers

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
Last revisionBoth sides next revision
build:feature_triggers [2016/04/20 17:18] – Yann Pouillonbuild:feature_triggers [2016/04/20 17:25] – [Using a global prefix] Yann Pouillon
Line 18: Line 18:
 The following table summarizes the available optional features of Abinit. To enable them, you will have to make sure that the corresponding [[build:optpkgs|optional packages]] are correctly installed on your system before configuring Abinit. The following table summarizes the available optional features of Abinit. To enable them, you will have to make sure that the corresponding [[build:optpkgs|optional packages]] are correctly installed on your system before configuring Abinit.
  
-^ Package   ^ Name      ^ Status       ^ Description                                         ^ +^ Package                               ^ Name      ^ Status       ^ Description                                         ^ 
-| bigdft    | BigDFT    | Development  | Wavelets for low-dimensional systems                | +| [[build:optpkgs#bigdft|bigdft]]       | BigDFT    | Development  | Wavelets for low-dimensional systems                | 
-| etsf_io   | ETSF_IO   | Mature       | Platform-independent data exchange                  | +| [[build:optpkgs#etsf_io|etsf_io]]     | ETSF_IO   | Mature       | Platform-independent data exchange                  | 
-| gsl       | GSL       | Mature       | Standard mathematical functions                     | +| [[build:optpkgs#gsl|gsl]]             | GSL       | Mature       | Standard mathematical functions                     | 
-| libpspio  | Libpspio  | Experimental | Reading of atomic data in many formats              | +| [[build:optpkgs#libpspio|libpspio]]   | Libpspio  | Experimental | Reading of atomic data in many formats              | 
-| libxc     | LibXC     | Mature       | More than 300 exchange-correlation functionals      | +| [[build:optpkgs#libxc|libxc]]         | LibXC     | Mature       | More than 300 exchange-correlation functionals      | 
-| netcdf    | NetCDF    | Mature       | Platform-independent I/O                            | +| [[build:optpkgs#netcdf|netcdf]]       | NetCDF    | Mature       | Platform-independent I/O                            | 
-| papi      | PAPI      | Mature       | Performance Application Programming Interface       | +| [[build:optpkgs#papi|papi]]           | PAPI      | Mature       | Performance Application Programming Interface       | 
-| psml      | PSML      | Mature       | PSeudopotential Markup Language                     | +| [[build:optpkgs#psml|psml]]           | PSML      | Mature       | PSeudopotential Markup Language                     | 
-| triqs     | TRIQS     | Experimental | Toolbox for Research on Interacting Quantum Systems | +| [[build:optpkgs#triqs|triqs]]         | TRIQS     | Experimental | Toolbox for Research on Interacting Quantum Systems | 
-| wannier90 | Wannier90 | Mature       | Maximally-Localized Wannier Functions (MLWFs)       | +| [[build:optpkgs#wannier90|wannier90]] | Wannier90 | Mature       | Maximally-Localized Wannier Functions (MLWFs)       | 
-| yaml      | LibYAML   | Experimental | YAML Ain't Markup Language I/O                      |+| [[build:optpkgs#yaml|yaml]]           | LibYAML   | Experimental | YAML Ain't Markup Language I/O                      |
  
  
Line 36: Line 36:
 All the individual options can be overridden by //with_optpkgs//, which tells the //configure// script that all external dependencies have been installed in the same place. In this case, the build system will assume that each package has been installed in its own //%%<package>-<version>%%// subdirectory and will enable all those it finds in the specified top directory. This means that you can install as many versions of each package as you want within the same directory tree, while keeping full compatibility with different Abinit versions. All the individual options can be overridden by //with_optpkgs//, which tells the //configure// script that all external dependencies have been installed in the same place. In this case, the build system will assume that each package has been installed in its own //%%<package>-<version>%%// subdirectory and will enable all those it finds in the specified top directory. This means that you can install as many versions of each package as you want within the same directory tree, while keeping full compatibility with different Abinit versions.
  
-<WRAP important>**Important note** \\ If you use this option, you can then only use the //with_package// options without arguments, to fine-tune which optional packages will actually be enabled. All other combinations will make //configure// fail with an error.</WRAP>+<WRAP important>**Important note** \\ If you use this option, you can then only use the other //with_package// options without arguments, to fine-tune which optional packages will actually be enabled. All other combinations will make //configure// fail with an error.</WRAP>
  
 As an example, let us now suppose that you have installed optional packages for Abinit under the //%%/%%path/to/my/packages%%/%%// directory. You directory tree will look like the following: As an example, let us now suppose that you have installed optional packages for Abinit under the //%%/%%path/to/my/packages%%/%%// directory. You directory tree will look like the following:
build/feature_triggers.txt · Last modified: 2016/04/24 14:21 by Yann Pouillon