mirror of
git://sourceware.org/git/libabigail.git
synced 2024-12-24 02:32:16 +00:00
3f9b3c0d8a
* doc/website/mainpage.txt: The IRC server address is irc.oftc.net, not just oftc.net. * include/abg-fwd.h: Likewise. Signed-off-by: Dodji Seketeli <dodji@redhat.com>
135 lines
3.8 KiB
Plaintext
135 lines
3.8 KiB
Plaintext
/*!
|
|
|
|
\mainpage The ABI Generic Analysis and Instrumentation Library
|
|
|
|
\tableofcontents
|
|
|
|
\section presentation Presentation
|
|
|
|
This project aims at providing a C++ library for constructing,
|
|
manipulating, serializing and de-serializing ABI-relevant artifacts.
|
|
The set of artifacts that we are interested in is made of
|
|
constructions like types, variables, functions and declarations of a
|
|
given library or program. For a given program or library, this set of
|
|
constructions is called an ABI corpus.
|
|
|
|
Thus the project aims at providing a library to manipulate ABI
|
|
corpora, compare them, provide detailed information about their
|
|
differences and help build tools to infer interesting conclusions
|
|
about these differences.
|
|
|
|
\section documentation Documentation
|
|
|
|
The documentations of the libabigail tools is available online <a
|
|
href="http://sourceware.org/libabigail/manual">here</a>.
|
|
|
|
The html documentation of the API of the library itself is available
|
|
online <a href="http://sourceware.org/libabigail/apidoc">here</a>.
|
|
|
|
\section communication IRC and Mailing lists
|
|
|
|
To hang out with libabigail developers and users, you can chat with us
|
|
via <a href="http://en.wikipedia.org/wiki/Wikipedia:IRC">IRC</a> at
|
|
<em>irc://irc.oftc.net\#libabigail</em>.
|
|
|
|
To send us patches or just drop by to say Hi, please send an email to
|
|
our mailing list <em>libabigail@sourceware.org</em>. You first need to
|
|
register to the mailing list by feeling the form below.
|
|
|
|
\htmlonly
|
|
|
|
<form method="get" action="http://sourceware.org/cgi-bin/ml-request">
|
|
Mailing list name:
|
|
<input type="text" name="listname" value="libabigail" size="10"/>
|
|
<br>
|
|
Your e-mail address:
|
|
<input type="text" name="username" size="14"/>
|
|
<br>
|
|
<input type="checkbox" name="digest"/>Digest version
|
|
<tt> </tt>
|
|
<select name="operation">
|
|
<option value="subscribe">subscribe</option>
|
|
<option value="unsubscribe">unsubscribe</option>
|
|
</select>
|
|
<tt> </tt>
|
|
<input type="Submit" name="submit" value="Send in the request"/>
|
|
</form>
|
|
\endhtmlonly
|
|
|
|
\section bugs Bug reports
|
|
|
|
Bug reports are to be filed into our <a
|
|
href="http://sourceware.org/bugzilla/enter_bug.cgi?product=libabigail">Bugzilla
|
|
database</a>.
|
|
|
|
\section license License
|
|
|
|
The source code of the library is under <a href="http://www.gnu.org/licenses/lgpl.html"> LGPL version 3</a> or later.
|
|
|
|
|
|
\section source Getting the source code
|
|
|
|
This project is still in an early stage; we haven't released any
|
|
official tarball yet. You can get the source code in a read-only
|
|
manner from our <a
|
|
href="http://sourceware.org/git/gitweb.cgi?p=libabigail.git">Git
|
|
repository</a> by doing:
|
|
|
|
\code{.sh}
|
|
git clone git://sourceware.org/git/libabigail.git
|
|
\endcode
|
|
|
|
If you have write access on sourceware.org, you can check the source
|
|
out in read-write by doing:
|
|
|
|
\code{.sh}
|
|
git clone ssh://sourceware.org/git/libabigail.git
|
|
\endcode
|
|
|
|
\section compile Compiling the source code
|
|
|
|
To compile libabigail, you first need to install its dependencies. At
|
|
the moment the dependencies are the following Free Software packages:
|
|
|
|
\li <a href="http://www.xmlsoft.org">libxml2</a>
|
|
\li <a href="http://www.gnu.org/software/autoconf/">autoconf</a>
|
|
\li <a href="https://fedorahosted.org/elfutils/">elfutils</a>
|
|
|
|
Then go to your local libabigail.git directory where the source code
|
|
you've checked out lies and create a 'build' directory that will
|
|
receive the binaries resulting from the compilation:
|
|
|
|
\code{.sh}
|
|
cd libabigail
|
|
mkdir build
|
|
\endcode
|
|
|
|
Generate the relevant build-system-related information needed to
|
|
configure the package for compilation, by typing:
|
|
|
|
\code{.sh}
|
|
autoreconf -i
|
|
\endcode
|
|
|
|
Then configure the package:
|
|
|
|
\code{.sh}
|
|
cd build
|
|
../configure --prefix=<absolute-path-of-where-you-want-the-binaries-to-be-installed>
|
|
\endcode
|
|
|
|
Then build the package
|
|
|
|
\code{.sh}
|
|
make
|
|
\endcode
|
|
|
|
And then install its resulting binaries and documentation:
|
|
|
|
\code{.sh}
|
|
make install
|
|
\endcode
|
|
|
|
|
|
*/
|