Autotools for writing portable software

TL;DR

This paper discusses how to use Autotools to develop portable scientific software that can be easily installed and run across different platforms, addressing common challenges faced by scientists.

Contribution

It introduces practical methods for employing Autotools to ensure software portability and ease of installation across diverse systems.

Findings

Autotools simplifies cross-platform software development.

Using Autotools reduces installation and configuration issues.

It enhances reproducibility of scientific software across environments.

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.