Autotools for writing portable software
Jens Krueger
Abstract
Most of the scientific software is developed in the same manner: It starts at a lab and the scientist says "This part of software is only for my private use". But the software grows and grows, and it comes the time, that other scientists want to use it, too. If they are not working in the same lab and on the same machine, it leads to the problem how to install this software on the new machine. Sometimes it is relatively easy to adopt the makefile to the new conditions (compiler, linker, libraries), if it is well written. But mostly it is not done by changing some pathes. One has to change the compiler, linker, additional or standard libraries, and so on. I want to show how you avoid a lot of trouble, if you write software, which may be used on different plattforms.
Create a lesson
Related papers
Knots in Condensed Matters
Y. M. Cho
Bouchaud's model exhibits two different aging regimes in dimension one
Gerard Ben Arous, Jiri Cerny
Periodic diffraction patterns for 1D quasicrystals
Pawel Buczek, Lorenzo Sadun, Janusz Wolny
Adiabatic association of ultracold molecules via magnetic field tunable interactions
Krzysztof Goral, Thorsten Koehler, Simon A. Gardiner et al.
High-Temperature Atomic Superfluidity in Lattice Boson-Fermion Mixtures
F. Illuminati, A. Albus
Constructive Methods of Invariant Manifolds for Kinetic Problems
A. N. Gorban, I. V. Karlin, A. Yu. Zinovyev