Commiting basic files for rtorrent.

git-svn-id: svn://rakshasa.no/libtorrent/trunk/rtorrent@233 e378c898-3ddf-0310-93e7-cc216c733640

AUTHORS

+Jari Sundell <jaris@ifi.uio.no>

INSTALL

+Copyright 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software
+Foundation, Inc.
+
+   This file is free documentation; the Free Software Foundation gives
+unlimited permission to copy, distribute and modify it.
+
+Basic Installation
+==================
+
+   These are generic installation instructions.
+
+   The `configure' shell script attempts to guess correct values for
+various system-dependent variables used during compilation.  It uses
+those values to create a `Makefile' in each directory of the package.
+It may also create one or more `.h' files containing system-dependent
+definitions.  Finally, it creates a shell script `config.status' that
+you can run in the future to recreate the current configuration, and a
+file `config.log' containing compiler output (useful mainly for
+debugging `configure').
+
+   It can also use an optional file (typically called `config.cache'
+and enabled with `--cache-file=config.cache' or simply `-C') that saves
+the results of its tests to speed up reconfiguring.  (Caching is
+disabled by default to prevent problems with accidental use of stale
+cache files.)
+
+   If you need to do unusual things to compile the package, please try
+to figure out how `configure' could check whether to do them, and mail
+diffs or instructions to the address given in the `README' so they can
+be considered for the next release.  If you are using the cache, and at
+some point `config.cache' contains results you don't want to keep, you
+may remove or edit it.
+
+   The file `configure.ac' (or `configure.in') is used to create
+`configure' by a program called `autoconf'.  You only need
+`configure.ac' if you want to change it or regenerate `configure' using
+a newer version of `autoconf'.
+
+The simplest way to compile this package is:
+
+  1. `cd' to the directory containing the package's source code and type
+     `./configure' to configure the package for your system.  If you're
+     using `csh' on an old version of System V, you might need to type
+     `sh ./configure' instead to prevent `csh' from trying to execute
+     `configure' itself.
+
+     Running `configure' takes awhile.  While running, it prints some
+     messages telling which features it is checking for.
+
+  2. Type `make' to compile the package.
+
+  3. Optionally, type `make check' to run any self-tests that come with
+     the package.
+
+  4. Type `make install' to install the programs and any data files and
+     documentation.
+
+  5. You can remove the program binaries and object files from the
+     source code directory by typing `make clean'.  To also remove the
+     files that `configure' created (so you can compile the package for
+     a different kind of computer), type `make distclean'.  There is
+     also a `make maintainer-clean' target, but that is intended mainly
+     for the package's developers.  If you use it, you may have to get
+     all sorts of other programs in order to regenerate files that came
+     with the distribution.
+
+Compilers and Options
+=====================
+
+   Some systems require unusual options for compilation or linking that
+the `configure' script does not know about.  Run `./configure --help'
+for details on some of the pertinent environment variables.
+
+   You can give `configure' initial values for configuration parameters
+by setting variables in the command line or in the environment.  Here
+is an example:
+
+     ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
+
+   *Note Defining Variables::, for more details.
+
+Compiling For Multiple Architectures
+====================================
+
+   You can compile the package for more than one kind of computer at the
+same time, by placing the object files for each architecture in their
+own directory.  To do this, you must use a version of `make' that
+supports the `VPATH' variable, such as GNU `make'.  `cd' to the
+directory where you want the object files and executables to go and run
+the `configure' script.  `configure' automatically checks for the
+source code in the directory that `configure' is in and in `..'.
+
+   If you have to use a `make' that does not support the `VPATH'
+variable, you have to compile the package for one architecture at a
+time in the source code directory.  After you have installed the
+package for one architecture, use `make distclean' before reconfiguring
+for another architecture.
+
+Installation Names
+==================
+
+   By default, `make install' will install the package's files in
+`/usr/local/bin', `/usr/local/man', etc.  You can specify an
+installation prefix other than `/usr/local' by giving `configure' the
+option `--prefix=PATH'.
+
+   You can specify separate installation prefixes for
+architecture-specific files and architecture-independent files.  If you
+give `configure' the option `--exec-prefix=PATH', the package will use
+PATH as the prefix for installing programs and libraries.
+Documentation and other data files will still use the regular prefix.
+
+   In addition, if you use an unusual directory layout you can give
+options like `--bindir=PATH' to specify different values for particular
+kinds of files.  Run `configure --help' for a list of the directories
+you can set and what kinds of files go in them.
+
+   If the package supports it, you can cause programs to be installed
+with an extra prefix or suffix on their names by giving `configure' the
+option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
+
+Optional Features
+=================
+
+   Some packages pay attention to `--enable-FEATURE' options to
+`configure', where FEATURE indicates an optional part of the package.
+They may also pay attention to `--with-PACKAGE' options, where PACKAGE
+is something like `gnu-as' or `x' (for the X Window System).  The
+`README' should mention any `--enable-' and `--with-' options that the
+package recognizes.
+
+   For packages that use the X Window System, `configure' can usually
+find the X include and library files automatically, but if it doesn't,
+you can use the `configure' options `--x-includes=DIR' and
+`--x-libraries=DIR' to specify their locations.
+
+Specifying the System Type
+==========================
+
+   There may be some features `configure' cannot figure out
+automatically, but needs to determine by the type of machine the package
+will run on.  Usually, assuming the package is built to be run on the
+_same_ architectures, `configure' can figure that out, but if it prints
+a message saying it cannot guess the machine type, give it the
+`--build=TYPE' option.  TYPE can either be a short name for the system
+type, such as `sun4', or a canonical name which has the form:
+
+     CPU-COMPANY-SYSTEM
+
+where SYSTEM can have one of these forms:
+
+     OS KERNEL-OS
+
+   See the file `config.sub' for the possible values of each field.  If
+`config.sub' isn't included in this package, then this package doesn't
+need to know the machine type.
+
+   If you are _building_ compiler tools for cross-compiling, you should
+use the `--target=TYPE' option to select the type of system they will
+produce code for.
+
+   If you want to _use_ a cross compiler, that generates code for a
+platform different from the build platform, you should specify the
+"host" platform (i.e., that on which the generated programs will
+eventually be run) with `--host=TYPE'.
+
+Sharing Defaults
+================
+
+   If you want to set default values for `configure' scripts to share,
+you can create a site shell script called `config.site' that gives
+default values for variables like `CC', `cache_file', and `prefix'.
+`configure' looks for `PREFIX/share/config.site' if it exists, then
+`PREFIX/etc/config.site' if it exists.  Or, you can set the
+`CONFIG_SITE' environment variable to the location of the site script.
+A warning: not all `configure' scripts look for a site script.
+
+Defining Variables
+==================
+
+   Variables not defined in a site shell script can be set in the
+environment passed to `configure'.  However, some packages may run
+configure again during the build, and the customized values of these
+variables may be lost.  In order to avoid this problem, you should set
+them in the `configure' command line, using `VAR=value'.  For example:
+
+     ./configure CC=/usr/local2/bin/gcc
+
+will cause the specified gcc to be used as the C compiler (unless it is
+overridden in the site shell script).
+
+`configure' Invocation
+======================
+
+   `configure' recognizes the following options to control how it
+operates.
+
+`--help'
+`-h'
+     Print a summary of the options to `configure', and exit.
+
+`--version'
+`-V'
+     Print the version of Autoconf used to generate the `configure'
+     script, and exit.
+
+`--cache-file=FILE'
+     Enable the cache: use and save the results of the tests in FILE,
+     traditionally `config.cache'.  FILE defaults to `/dev/null' to
+     disable caching.
+
+`--config-cache'
+`-C'
+     Alias for `--cache-file=config.cache'.
+
+`--quiet'
+`--silent'
+`-q'
+     Do not print messages saying which checks are being made.  To
+     suppress all normal output, redirect it to `/dev/null' (any error
+     messages will still be shown).
+
+`--srcdir=DIR'
+     Look for the package's source code in directory DIR.  Usually
+     `configure' can determine that directory automatically.
+
+`configure' also accepts some other, not widely useful, options.  Run
+`configure --help' for more details.
+

Makefile.am

+SUBDIRS = src
+
+EXTRA_DIST= \
+	autogen.sh

autogen.sh

+#! /bin/sh
+
+echo aclocal...
+(aclocal --version) < /dev/null > /dev/null 2>&1 || {
+    echo aclocal not found
+    exit 1
+}
+
+aclocal
+
+echo autoheader...
+(autoheader --version) < /dev/null > /dev/null 2>&1 || {
+    echo autoheader not found
+    exit 1
+}
+
+autoheader
+
+echo libtoolize...
+(libtoolize --version) < /dev/null > /dev/null 2>&1 || {
+    echo libtoolize not found
+    exit 1
+}
+
+libtoolize --automake --copy --force
+
+echo automake...
+(automake --version) < /dev/null > /dev/null 2>&1 || {
+    echo automake not found
+    exit 1
+}
+
+automake --add-missing --copy --gnu
+
+echo autoconf...
+(autoconf --version) < /dev/null > /dev/null 2>&1 || {
+    echo autoconf not found
+    exit 1
+}
+
+autoconf
+
+echo ready to configure
+
+exit 0

configure.ac

+AC_INIT(src/rtorrent.cc, 0.0.0, jaris@ifi.uio.no)
+
+AM_INIT_AUTOMAKE
+AM_CONFIG_HEADER(config.h)
+
+sinclude(scripts/checks.m4)
+
+CXXFLAGS="-O3"
+
+AC_PROG_CXX
+
+AC_SYS_LARGEFILE
+
+AC_ARG_ENABLE(debug,
+    [  --enable-debug          enable debug information [default=yes]],
+    [
+        if test "$enableval" = "yes"; then
+            CXXFLAGS="$CXXFLAGS -Wall -g -DDEBUG"
+        else
+            CXXFLAGS="$CXXFLAGS -Wall -DNDEBUG"
+        fi
+    ],[
+        CXXFLAGS="$CXXFLAGS -Wall -g -DDEBUG"
+    ]
+)
+
+AC_ARG_ENABLE(werror,
+    [  --enable-werror         enable the -Werror flag [default=no]],
+    [
+        if test "$enableval" = "yes"; then
+            CXXFLAGS="$CXXFLAGS -Werror"
+        fi
+    ]
+)
+
+PKG_CHECK_MODULES(STUFF, sigc++-2.0 libtorrent >= 0.4.8,
+	          CXXFLAGS="$CXXFLAGS $STUFF_CFLAGS";
+		  LIBS="$LIBS $STUFF_liBS")
+
+TORRENT_CHECK_CURL()
+TORRENT_OTFD()
+
+AC_DEFINE(HAVE_CONFIG_H, 1, true if config.h was included)
+
+AC_OUTPUT([
+	Makefile
+	src/Makefile
+])

scripts/checks.m4

+AC_DEFUN([TORRENT_CHECK_CURL], [
+
+  AC_CACHE_VAL(my_cv_curl_vers, [
+    my_cv_curl_vers=NONE
+    dnl check is the plain-text version of the required version
+    check="7.12.0"
+    dnl check_hex must be UPPERCASE if any hex letters are present
+    check_hex="070C00"
+ 
+    AC_MSG_CHECKING([for curl >= $check])
+ 
+    if eval curl-config --version 2>/dev/null >/dev/null; then
+      ver=`curl-config --version | sed -e "s/libcurl //g"`
+      hex_ver=`curl-config --vernum | tr 'a-f' 'A-F'`
+      ok=`echo "ibase=16; if($hex_ver>=$check_hex) $hex_ver else 0" | bc`
+ 
+      if test x$ok != x0; then
+        my_cv_curl_vers="$ver"
+        AC_MSG_RESULT([$my_cv_curl_vers])
+      else
+        AC_MSG_RESULT(FAILED)
+        AC_MSG_ERROR([$ver is too old. Need version $check or higher.])
+      fi
+    else
+      AC_MSG_RESULT(FAILED)
+      AC_MSG_ERROR([curl-config was not found])
+    fi
+  ])
+])
+
+
+AC_DEFUN([TORRENT_CHECK_OPENSSL], [
+  # first, deal with the user option : set places to be 'search' or the prefix
+  AC_ARG_WITH(openssl,
+    [  --with-openssl=PATH     Find the OpenSSL header and library in
+                      `PATH/include' and `PATH/lib'. If PATH is of the
+                      form `HEADER:LIB', then search for header files in
+                      HEADER, and the library in LIB.  If you omit the
+                      option completely, the configure script will
+                      search for OpenSSL in a number of standard
+                      places.
+    ], [
+      if test "$withval" = "yes"; then
+	PKG_CHECK_MODULES(OPENSSL, openssl,
+	                  CXXFLAGS="$CXXFLAGS `pkg-config --cflags openssl`";
+                          LIBS="$LIBS -lcrypto `pkg-config --libs-only-L openssl`",
+		          AC_MSG_ERROR(Could not find openssl's crypto library, try --with-openssl=PATH))
+
+        else
+	  CXXFLAGS="$CXXFLAGS -I$withval/include"
+	  LIBS="$LIBS -lcrypto -L$withval/lib"
+        fi
+    ], [
+      PKG_CHECK_MODULES(OPENSSL, openssl,
+      CXXFLAGS="$CXXFLAGS `pkg-config --cflags openssl`";
+      LIBS="$LIBS -lcrypto `pkg-config --libs-only-L openssl`",
+      AC_MSG_ERROR(Could not find openssl's crypto library, try --with-openssl=PATH))
+    ])
+])
+
+
+AC_DEFUN([TORRENT_MINCORE_SIGNEDNESS], [
+
+  AC_LANG_PUSH(C++)
+  AC_MSG_CHECKING(signedness of mincore parameter)
+
+  AC_COMPILE_IFELSE(
+    [[#include <sys/types.h>
+      #include <sys/mman.h>
+      void f() { mincore((void*)0, 0, (unsigned char*)0); }
+    ]],
+    [
+      AC_DEFINE(USE_MINCORE_UNSIGNED, 1, use unsigned char* in mincore)
+      AC_MSG_RESULT(unsigned)
+    ],
+    [
+      AC_COMPILE_IFELSE(
+        [[#include <sys/types.h>
+          #include <sys/mman.h>
+          void f() { mincore((void*)0, 0, (char*)0); }
+        ]],
+        [
+          AC_DEFINE(USE_MINCORE_UNSIGNED, 0, use char* in mincore)
+          AC_MSG_RESULT(signed)
+        ],
+        [
+          AC_MSG_ERROR([mincore signedness test failed])
+      ])
+  ])
+
+  AC_LANG_POP(C++)
+])
+
+
+AC_DEFUN([TORRENT_OTFD], [
+
+  AC_LANG_PUSH(C++)
+  AC_MSG_CHECKING(for proper overloaded template function disambiguation)
+
+  AC_COMPILE_IFELSE(
+    [[template <typename T> void f(T&) {}
+      template <typename T> void f(T*) {}
+      int main() { int *i = 0; f(*i); f(i); }
+    ]],
+    [
+      AC_MSG_RESULT(yes)
+    ], [
+      AC_MSG_RESULT(no)
+      AC_MSG_ERROR([your compiler does not properly handle overloaded template function disambiguation])
+  ])
+
+  AC_LANG_POP(C++)
+])

src/Makefile.am

+bin_PROGRAMS = rtorrent
+
+rtorrent_SOURCES = \
+	rtorrent.cc
+
+rtorrent_LDADD =
\ No newline at end of file

src/rtorrent.cc

+
+int main(int argc, char** argv) {
+  return 0;
+}