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

Update for removal of dependency on Libtool

Browse source 
Mailing list page update


git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk@6040 626c5289-ae23-0410-ae9c-e8d60b6d4f22
This commit is contained in:
William S Fulton 2004-07-15 21:03:57 +00:00
commit d8bedbca57
1 changed files with 41 additions and 26 deletions
Download patch file Download diff file Expand all files Collapse all files

67
swigweb/cvs.ht
View file

@ -14,15 +14,34 @@ Development versions of SWIG are available through the CVS server located at Sou
The CVS release represents work in progress and is not guaranteed to compile on your machine or be functional in any
manner.
<h3> Required Tools </h3>
To compile SWIG from its CVS repository, you will need the following tools:
<ul>
<li> Autoconf 2.54 or higher
<li> Automake 1.7.2 or higher
<li> A working C++ compiler.
<li> yacc or bison (to compile the SWIG parser).
</ul>
<p>
It is important to note that the CVS repository does not include the C++ code
generated by yacc nor the files produced by Autoconf or Automake (these
are however included in a normal release). Thus, you will have
to install these tools on your machine for everything to work.
<h3>To check out the latest version </h3>
There are
<a href="http://sourceforge.net/cvs/?group_id=1645">generic CVS instructions</a>
available on the SourceForge site, but the following steps should be all you need.
<ol>
<li> Set the location of CVSROOT
<p>
<pre>
% setenv CVSROOT :pserver:anonymous@cvs.sourceforge.net:/cvsroot/swig
</pre>
% setenv CVSROOT :pserver:anonymous@cvs.sourceforge.net:/cvsroot/swig </pre>
<p>
(Alternatively, you can use the -d option to CVS)
@ -55,29 +74,24 @@ CVS password: &lt;press enter here&gt
% make
% make install
</pre>
<p>
<li>To check the build, run the tests:
<p>
<pre>
% make -k check </pre>
This could take up to an hour or longer. If you are interested in a particular language,
just check the examples and test-suite for that language. For example, the Python tests:
<pre>
% make check-python-examples
% make check-python-test-suite
</pre>
</ol>
<b>Note:</b> The CVS repository is read-only so the system will not
accept code modifications unless you are a developer.
<h3> Required Tools </h3>
To compile SWIG from its CVS repository, you will need the following tools:
<ul>
<li> Autoconf 2.54 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).
</ul>
<p>
It is important to note that the CVS repository does not include the C++ code
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>
@ -93,29 +107,30 @@ Both these steps will be necessary if you have a fresh CVS checkout or if the bu
</li>
<li>
Check that the appropriate versions of your autotools (Autoconf, Automake and Libtool) are installed properly.
Check that the appropriate versions of your autotools (Autoconf and Automake) are installed properly.
The autotools are in a state of flux and there are backward compatibility issues which are solved in different ways on different operating systems.
</li>
<li>
Check that all the autotool bootstrap programs which are executed when running <tt>./autogen.sh</tt> are up to date and match your installed autotool versions.
For example <tt>aclocal --version</tt> should report a matching version of Automake, Libtool or Autoconf, something like "aclocal (GNU automake) 1.7.6".
For example <tt>aclocal --version</tt> should report a matching version of Automake or Autoconf, something like "aclocal (GNU automake) 1.7.6".
</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>.
If you are still having problems, send an email to <a href="mail.html">swig-dev</a> mailing list.
<h3>Developer Access</h3>
We are always looking for people to help out with various projects.
<ul>
<li> Send email to <a href="mailto:swig-dev@cs.uchicago.edu">swig-dev@cs.uchicago.edu</a>
<li> Send email to to the <a href="mail.html">swig-dev</a> mailing list.
if you are interested in doing developer work and gaining write access to the CVS repository.
<p>
<li>A developer mailing list is available at <a href="mailto:swig-dev@cs.uchicago.edu">swig-dev@cs.uchicago.edu</a> to discuss coding issues, bugs, patches, and so forth.
Subscription information and archives of recent activity can be found on the <a href="http://mailman.cs.uchicago.edu/mailman/listinfo/swig-dev">SWIG Developer Mailing List</a> page.
<li> The <a href="mail.html">swig-dev</a> mailing list is the developer mailing list
and should be used to discuss coding issues, bugs, patches, and so forth.
Subscription information and archives of recent activity can be found on the <a href="mail.html">mailing lists</a> page.
</ul>