From 8631251255ee8e6c4a424a1b2145b0e0459163e4 Mon Sep 17 00:00:00 2001 From: Niklas Eicker Date: Fri, 2 Jun 2017 12:53:44 +0200 Subject: [PATCH] Add 'autoconf' to 'Quick Build Guide' For someone strictly following the 'Quick Build Guide' running './configure' will produce 'bash: ./configure: No such file or directory'. To spare others the same problem 'autoconf' was added to the guide which will produce the missing configure script with the given 'configure.ac'. --- README | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/README b/README index 65a2405b..e77994ab 100644 --- a/README +++ b/README @@ -39,7 +39,7 @@ Table of Contents * Nils Jannasch (https://github.com/NJannasch) * OpenMEEG ((http://openmeeg.github.io/) * Scilab (http://www.scilab.org/) - * Sébastien Villemot (https://github.com/sebastien-villemot) + * SĂ©bastien Villemot (https://github.com/sebastien-villemot) * SGI in support of Interactive Supercomputing, Inc. * Steven Leibman @@ -90,12 +90,14 @@ Table of Contents 2.2 Building matio 2.2.1 Quick Build Guide - The primary method for building the software is using 'configure' - followed by 'make'. After building, the testsuite can be executed to + The primary method for building the software is running 'autoconf' to + produce the configure skript then using 'configure' followed by 'make'. + After building, the testsuite can be executed to test the software using 'make check'. The software can be installed using 'make install'. For example, $ tar zxf matio-X.Y.Z.tar.gz $ cd matio-X.Y.Z + $ autoconf $ ./configure $ make $ make check