build:bindings
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
build:bindings [2014/07/08 11:23] – Yann Pouillon | build:bindings [2014/11/04 22:47] – [Workflow] Yann Pouillon | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Building bindings ====== | ||
+ | ===== Introduction ===== | ||
+ | The bindings available in Abinit allow external packages to access some Abinit components and remain synchronized with the latest developments in a semi-automatic manner. | ||
+ | For a typical example using the Abinit parser bindings, please see [[http:// | ||
+ | |||
+ | **Important note**: since the bindings are still relatively experimental and might cause unexpected issues, we recommend you to build Abinit without the // | ||
+ | |||
+ | ===== Workflow ===== | ||
+ | |||
+ | Abinit bindings are built independently of the core source code. They only require the core build to be configured with the // | ||
+ | |||
+ | < | ||
+ | +------------------------+ | ||
+ | | Normal build of Abinit | | Go to the bindings/ subdir | | Configure and build | | ||
+ | | configured with +--->+ of the build directory | ||
+ | | enable_exports set | ||
+ | +------------------------+ | ||
+ | </ | ||
+ | |||
+ | The typical command sequence for such a build would read as follows (replacing the //${...}// variables by the names you chose for your build): | ||
+ | |||
+ | <code bash> | ||
+ | cd ${abinit_srcdir} | ||
+ | mkdir ${abinit_builddir} && cd ${abinit_builddir} | ||
+ | ${abinit_srcdir}/ | ||
+ | make -j8 | ||
+ | cd bindings | ||
+ | edit config.sh | ||
+ | ${abinit_srcdir}/ | ||
+ | make | ||
+ | </ | ||
+ | |||
+ | To build an individual bindings item, just type '' |