구차니의 잡동사니 모음

  B. Dependency Overview



      You'll need the following build tools to compile Subversion:



      * autoconf 2.58 or later (Unix only)

      * libtool 1.4 or later (Unix only)

      * a reasonable C compiler (gcc, Visual Studio, etc.)





      Subversion also depends on the following third-party libraries:



      * libapr and libapr-util (REQUIRED for client and server)



         The Apache Portable Runtime (APR) library provides an

         abstraction of operating-system level services such as file

         and network I/O, memory management, and so on.  It also

         provides convenience routines for things like hashtables,

         checksums, and argument processing.  While it was originally

         developed for the Apache HTTP server, APR is a standalone

         library used by Subversion and other products.  It is a

         critical dependency for all of Subversion; it's the layer

         that allows Subversion clients and servers to run on

         different operating systems.



      * SQLite  (REQUIRED for client and server)



         Subversion uses SQLite to manage some internal databases.



      * libz  (REQUIRED for client and server)



         Subversion uses zlib for compressing binary differences.

         These diff streams are used everywhere -- over the network,

         in the repository, and in the client's working copy.



      * libserf  (OPTIONAL for client)



         The Serf libraries both allow the Subversion client

         to send HTTP requests.  This is necessary if you want your

         client to access a repository served by the Apache HTTP

         server.  There is an alternate 'svnserve' server as well,

         though, and clients automatically know how to speak the

         svnserve protocol.  Thus it's not strictly necessary for your

         client to be able to speak HTTP... though we still recommend

         that your client be built to speak both HTTP and svnserve

         protocols.



      * OpenSSL (OPTIONAL for client and server)



         OpenSSL enables your client to access SSL-encrypted https://

         URLs (using libserf) in addition to unencrypted http:// URLs.

         To use SSL with Subversion's WebDAV server, Apache needs to

         be compiled with OpenSSL as well.



      * Berkeley DB (OPTIONAL for client and server)



         There are two different repository 'back-end'

         implementations.  One implementation stores data in a flat

         filesystem (known as FSFS); the other implementation stores

         data in a Berkeley DB database (known as BDB).  When you

         create a repository, you have the option of specifying a

         storage back-end.  The Berkeley DB back-end will only be

         available if the BDB libraries are discovered at compile

         time.



      * libsasl (OPTIONAL for client and server)



         If the Cyrus SASL library is detected at compile time, then

         the svn client (and svnserve server) will be able to utilize

         SASL to do various forms of authentication when speaking the

         svnserve protocol.



      * Python, Perl, Java, Ruby  (OPTIONAL)



         Subversion is mostly a collection of C libraries with

         well-defined APIs, with a small collection of programs that

         use the APIs.  If you want to build Subversion API bindings

         for other languages, you need to have those languages

         available at build time.



      * KDELibs, GNOME Keyring  (OPTIONAL for client)



         Subversion contains optional support for storing passwords in

         KWallet (KDE 4) or GNOME Keyring.