Autotools for writing portable software

dc.creatorKrueger, Jens
dc.date2002-10-20
dc.date2002-11-01
dc.date.accessioned2026-07-07T02:47:48Z
dc.date.available2026-07-07T02:47:48Z
dc.descriptionMost 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.
dc.descriptionInvited talk at NOBUGS2002 Conference, NIST, Gaithersburg, MD NOBUGS abstract identifier NOBUGS2002/017 9 pages, LaTeX
dc.identifierhttps://arxiv.org/abs/cond-mat/0210430
dc.identifierhttp://arxiv.org/abs/cond-mat/0210430
dc.identifier.urihttp://salesiana.dossiersoluciones.com/handle/123456789/20148
dc.subjectCondensed Matter
dc.titleAutotools for writing portable software
dc.typetext

Files

Collections