jyapayne/swig
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Corrected Automake version.

Browse source 
New section on what to do in the case of build problems using SWIG CVS.


git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk@4827 626c5289-ae23-0410-ae9c-e8d60b6d4f22
This commit is contained in:
William S Fulton 2003-05-29 11:16:28 +00:00
commit 66a19e2e11
1 changed files with 23 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

24
swigweb/cvs.ht
View file

@ -71,7 +71,7 @@ To compile SWIG from its CVS repository, you will need the following tools:
<ul>
<li> Autoconf 2.54 or higher
<li> Automake 1.72 or higher
<li> Automake 1.7.2 or higher
<li> Libtool 1.4.2 or higher recommended, 1.5 preferable.
<li> A working C++ compiler.
<li> yacc or bison (to compile the SWIG parser).
@ -83,6 +83,28 @@ generated by yacc nor the files produced by Autoconf, Automake or Libtool (these
are however included in a normal release). Thus, you will have
to install these tools on your machine to work with everything.
<h3> Build Issues </h3>
Here are some guidelines should you be experiencing problems building SWIG from CVS.
<p>
<ol>
<li>Check is that you have a complete SWIG CVS repository update.
A fresh checkout from CVS often solves build problems.
</li>
<li>
Make sure you have run <tt>./autogen.sh</tt> and <tt>./configure</tt>.
This is required after updating from the CVS repository in the case of build files changing.
</li>
<li>
Check that your autotools are installed properly.
The autotools (Autoconf, Automake and Libtool) are in a state of flux and there are backward compatibility issues which are solved in different ways on different operating systems.
</li>
</ol>
If you are still having problems, send an email to <a href="mailto:swig-dev@cs.uchicago.edu">swig-dev@cs.uchicago.edu</a>.
<h3>Developer Access</h3>
We are always looking for people to help out with various projects.