install.sgml

絲路server源碼 Silk Road server source

<?xml version="1.0"?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
  "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" >

<book lang="en">
  <bookinfo>
    <title>Libodbc++ Installation</title>
    <authorgroup>
      <author>
        <firstname>Manush</firstname>
        <surname>Dodunekov</surname>
      </author>
      <author>
        <firstname>Kerry</firstname>
        <surname>Lothrop</surname>
        <othername role="mi">W.</othername>
      </author>
    </authorgroup>
    <date>2005-09-09</date>
    <releaseinfo>Version 0.2.4pre2</releaseinfo>
    <abstract>
      <para>This tries to explain the installation procedure for libodbc++</para>
    </abstract>
    <keywordset>
      <keyword>libodbc++</keyword>
      <keyword>ODBC</keyword>
    </keywordset>
  </bookinfo>

  <chapter id="software-requirements">
    <title>Software requirements</title>

    <sect1 id="c-compiler">
      <title>C++ compiler</title>

      <para>To compile libodbc++, you'll need a c++ compiler that supports
        exceptions, templates and namespaces and
        has a reasonable standard c++ library. On free unices,
        your best choice is <application>GCC</application> 2.95.2 or later, which can be
        obtained from <ulink url="http://gcc.gnu.org/">the GCC homepage</ulink>.
        If you already have <application>egcs</application> 1.1.2 or later, it will do.</para>

      <para>On win32, success has been reported with MSVC 5.0 to 7.1, with
        and without QT.</para>
    </sect1>

    <sect1 id="odbc-driver-manager">
      <title>ODBC Driver Manager</title>

      <para>The <acronym>ODBC</acronym> Driver Manager is the software layer between
        applications and <acronym>ODBC</acronym> drivers. You must have one installed
        in order to use this library.
        The free choices on UNIX are:
        <itemizedlist>
          <listitem><para><ulink url="http://www.iodbc.org/">iODBC</ulink>.
              Version 2.50.3 or later is recommended.</para>
          </listitem>
          <listitem>
            <para><ulink url="http://www.unixodbc.org/">unixODBC</ulink>.
              Version 1.8.4 or later is recommended.</para>
          </listitem>
        </itemizedlist>
        Among the commercial driver managers, <application>libodbc++</application> has been reported to work fine
        with the <ulink url="http://www.merant.com/">Merant</ulink> driver manager.</para>
    </sect1>

    <sect1 id="drivers">
      <title>Drivers</title>

      <para>To actually use libodbc++, you will need
        one or more <acronym>ODBC</acronym> drivers. Examples of free database engines
        with <acronym>ODBC</acronym> drivers are:
        <itemizedlist>
          <listitem>
            <para><ulink url="http://www.mysql.com/">MySQL</ulink></para>
          </listitem>
          <listitem>
            <para><ulink url="http://www.postgresql.org/">PostgreSQL</ulink></para>
          </listitem>
        </itemizedlist>
        <warning><para><application>MyODBC</application> version 2.50.28 contains a bug that prevents
            it from working (at all).
            <ulink url="ftp://ftp.easysoft.com/pub/beta/unixODBC/MyODBC-2.50.28.patch">This</ulink>
            patch solves the problem.
          </para>
        </warning>
      </para>

      <para>Several vendors provide commercial drivers for unix:
        <itemizedlist>
          <listitem>
            <para><ulink url="http://www.openlinksw.com/">Openlink Software</ulink>.</para>
          </listitem>
          <listitem>
            <para><ulink url="http://www.merant.com/">Merant</ulink></para>
          </listitem>
        </itemizedlist>
      </para>

    </sect1>

    <sect1 id="qt">
      <title>QT</title>

      <para><application>Libodbc++</application> can be built with support for
        <ulink url="http://www.trolltech.com/">the QT library</ulink> version 2.0 or later,
        both on UNIX and win32.</para>
    </sect1>
  </chapter>

  <chapter id="installation">
    <title>Installation</title>

    <sect1 id="unix">
      <title>UNIX</title>

      <para>The following information applies for installing <application>libodbc++</application> on unices.</para>

      <sect2 id="configuration">
        <title>Configuration</title>

        <para>First, you need to configure <application>libodbc++</application> for your system.
          Go into the source directory and do:

          <screen><prompt>$ </prompt><userinput><command>./configure</command></userinput></screen>

          or, if <application>iODBC</application> isn't installed in it's default location
          <filename class="directory">/usr/local</filename>, do:
          <screen><prompt>$ </prompt><userinput><command>./configure</command> --with-iodbc=<replaceable>DIR</replaceable></userinput></screen>

          This will make <command>./configure</command> look for <application>iODBC</application> in
          <filename class="directory"><replaceable>DIR</replaceable>/include</filename> and
          <filename class="directory"><replaceable>DIR</replaceable>/lib</filename>.</para>

        <para>If you aren't using <application>iODBC</application>, try

          <screen><prompt>$ </prompt><userinput><command>./configure</command> --with-odbc=<replaceable>DIR</replaceable></userinput></screen>
          This works the same as above, except it looks for standard <acronym>ODBC</acronym> headers and libraries
          instead of the <application>iODBC</application>-specific ones. This should be used with for example
          <application>unixODBC</application> and <application>Merant driver manager</application>.</para>

        <para>If you wish to install <application>libodbc++</application> in a location other than
          <filename class="directory">/usr/local</filename>, add
          <userinput>--prefix=<replaceable>PREFIX</replaceable></userinput> to the <command>./configure</command> arguments.</para>

        <para>If the c++ compiler you wish to use to compile this package isn't the system
          default one, you will need to set the environment variable <envar>CXX</envar> to
          the name of it's executable. For example, if you have an old <application>gcc</application> or
          <application>egcs</application> as a system default compiler, but installed a newer
          <application>gcc</application> in <filename class="directory">/usr/local/gcc</filename>, do like this: