[BACK]Return to INSTALL CVS log [TXT] [DIR] Up to [parser3project] / parser3

Diff for /parser3/INSTALL between versions 1.32 and 1.35

version 1.32, 2003/05/12 06:35:16 version 1.35, 2004/02/10 10:41:52
Line 1 Line 1
 0.Assuming your perform your builds in $D directory   0.Assuming your perform your builds in $HOME directory 
   and suggested subdirectories.    and suggested subdirectories.
   
 1.What is the process to compile Parser3?   1.What is the process to compile Parser3?
   
     First, you must have LIBGC installed (conservative garbage collector for C++).
         libgc >= 6.1 [http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/gc6.1.tar.gz]
       
       Installation sequence of this library to $HOME/gc:
   
       cd libgc-x.x
       ./configure --prefix=$HOME/gc --disable-threads --silent
       make install
   
       Then you can use these Parser3 configure options to specify the location and static/dynamic linkage with libgc:
           --with-static-gc=$HOME/gc/lib
           --with-shared-gc=$HOME/gc/lib
   
   As most UNIX programs Parser3 follows the "standard":    As most UNIX programs Parser3 follows the "standard":
   
   mkdir $D/parser3project    mkdir $HOME/parser3project
   cd $D/parser3project    cd $HOME/parser3project
   gunzip -c parser3-x.x.tar.gz | tar xvf -    gunzip -c parser3-x.x.tar.gz | tar xvf -
   mv parser3-x.x parser3    mv parser3-x.x parser3
   cd parser3    cd parser3
Line 39 Line 52
     $prefix/etc/      $prefix/etc/
       parser3.charsets/   -- charset definition files        parser3.charsets/   -- charset definition files
         koi8-r.cfg        -- cyrillic charset [KOI8-R encoding]          koi8-r.cfg        -- cyrillic charset [KOI8-R encoding]
         windows-1250.cfg  -- central European charset [windows-1250 encoding]          windows-1250.cfg  -- central europian charset [windows-1250 encoding]
         windows-1251.cfg  -- cyrillic charset [windows-1251 encoding]          windows-1251.cfg  -- cyrillic charset [windows-1251 encoding]
         windows-1257.cfg  -- baltic charset [windows-1257 encoding]          windows-1257.cfg  -- baltic charset [windows-1257 encoding]
   
 3.What other libraries are needed to compile/install parser?   3.What other libraries are needed to compile/install parser? 
   
 3a. You can compile and use parser without any additional libraries.  3a. In case you wish XML(xdoc and xnode classes) support, you need libraries
     That would be 'basic' version of it.        libxml2 >= 2.6.5 [ftp://xmlsoft.org/libxml2-2.6.5.tar.gz]
         libxslt >= 1.1.2 [ftp://xmlsoft.org/libxslt-1.1.2.tar.gz]
 3b. In case you wish xml(xdoc and xnode classes) support you need libraries  
       libxml2 >= 2.5.1 [ftp://xmlsoft.org/libxml2-2.5.1.tar.gz]  
       libxslt >= 1.0.23 [ftp://xmlsoft.org/libxslt-1.0.23.tar.gz]  
       glib >= 1.2.10 [ftp://ftp.gtk.org/pub/gtk/v1.2/glib-1.2.10.tar.gz]        glib >= 1.2.10 [ftp://ftp.gtk.org/pub/gtk/v1.2/glib-1.2.10.tar.gz]
       gdome2 >= 0.7.2 [http://gdome2.cs.unibo.it/tarball/gdome2-0.7.2.tar.gz]        gdome2 >= 0.7.4 [http://gdome2.cs.unibo.it/tarball/gdome2-0.7.4.tar.gz]
     on your system, and specify path to them to Parser3 configure script.      on your system, and specify path to them to Parser3 configure script.
   
     Sources of these two libraries must be patched prior to compile:       Sources of libgdome library must be patched prior to compile. [library author bug confirmation pending]
       * libxml2  
       * libxslt  
   
     Installation sequence of these libraries to $D/gnome:      Installation sequence of these libraries to $HOME/gnome:
   
     libxml2:      libxml2:
   
     cd libxml2-x.x.x      cd libxml2-x.x.x
     patch -p0 < $D/parser3project/parser3/src/lib/patches/libxml2.patch      ./configure --prefix=$HOME/gnome --without-zlib --without-iconv --silent
     ./configure --prefix=$D/gnome --without-zlib --without-iconv  
     make install      make install
   
     libxslt:      libxslt:
   
     cd libxslt-x.x.x      cd libxslt-x.x.x
     patch -p0 < $D/parser3project/parser3/src/lib/patches/libxslt.patch      ./configure --with-libxml-prefix=$HOME/gnome --prefix=$HOME/gnome --without-debug --without-debugger --silent
     ./configure --with-libxml-prefix=$D/gnome --prefix=$D/gnome --without-debug --without-debugger  
     make install      make install
   
     glib:      glib:
   
     cd glib-x.x.x      cd glib-x.x.x
     ./configure --prefix=$D/gnome       ./configure --prefix=$HOME/gnome 
     make install      make install
   
     gdome2:      gdome2:
   
     cd gdome2-x.x.x      cd gdome2-x.x.x
     patch -p0 < $D/parser3project/parser3/src/lib/patches/gdome2.patch      patch -p0 < $HOME/parser3project/parser3/src/lib/patches/gdome2.patch
     ./configure --with-glib-prefix=$D/gnome --disable-glibtest --with-libxml-prefix=$D/gnome --prefix=$D/gnome      ./configure --with-glib-prefix=$HOME/gnome --disable-glibtest --with-libxml-prefix=$HOME/gnome --prefix=$HOME/gnome --silent
     make install      make install
   
     And copy these additional headers into install includes directory      And copy these additional headers into install includes directory
   
     mkdir $D/gnome/include/libgdome/gdomecore      mkdir $HOME/gnome/include/libgdome/gdomecore
     cp libgdome/gdomecore/gdome-xml-node.h $D/gnome/include/libgdome/gdomecore      cp libgdome/gdomecore/gdome-xml-node.h $HOME/gnome/include/libgdome/gdomecore
     cp libgdome/gdomecore/gdome-xml-document.h $D/gnome/include/libgdome/gdomecore      cp libgdome/gdomecore/gdome-xml-document.h $HOME/gnome/include/libgdome/gdomecore
           
   
     Parser3 configure options, choose whether you need static or dynamic linkage with xml libs:      Parser3 configure options, choose whether you need static or dynamic linkage with xml libs:
         --with-static-xml=$D/gnome          --with-static-xml=$HOME/gnome
         --with-shared-xml=$D/gnome          --with-shared-xml=$HOME/gnome
   
     NOTE:      NOTE:
     In case your glib as installed into some other prefix,      In case your glib as installed into some other prefix,
Line 109 Line 115
         --with-pathlink=LKEY    put dynamic libraries paths to binary          --with-pathlink=LKEY    put dynamic libraries paths to binary
                                 using linker key (-R, -rpath-link)                                  using linker key (-R, -rpath-link)
   
 3c. In case you wish $mail:receive support you need libraries  3b. In case you wish $mail:receive support you need libraries
       glib >= 1.2.10 [ftp://ftp.gtk.org/pub/gtk/v1.2/glib-1.2.10.tar.gz]        glib >= 1.2.10 [ftp://ftp.gtk.org/pub/gtk/v1.2/glib-1.2.10.tar.gz]
       gmime >= 1.0.1 [http://spruce.sourceforge.net/gmime/sources/gmime-1.0.5.tar.gz]        gmime >= 1.0.1 [http://spruce.sourceforge.net/gmime/sources/gmime-1.0.5.tar.gz]
     on your system, and specify path to them to Parser3 configure script.      on your system, and specify path to them to Parser3 configure script.
Line 119 Line 125
     glib:      glib:
   
     cd glib-x.x.x      cd glib-x.x.x
     ./configure --prefix=$D/gnome       ./configure --prefix=$HOME/gnome 
     make install      make install
   
     gmime:      gmime:
   
     cd gmime-x.x.x      cd gmime-x.x.x
     ./configure --prefix=$D/gnome      ./configure --prefix=$HOME/gnome
     make install      make install
   
     Parser3 configure options, choose whether you need static or dynamic linkage with xml libs:      Parser3 configure options, choose whether you need static or dynamic linkage with xml libs:
         --with-static-mailreceive=$D/gnome          --with-static-mailreceive=$HOME/gnome
         --with-shared-mailreceive=$D/gnome          --with-shared-mailreceive=$HOME/gnome
   
     NOTE:      NOTE:
     In case your glib as installed into some other prefix,      In case your glib as installed into some other prefix,
Line 138 Line 144
         --with-glib-config=/path/to/your/glib-config          --with-glib-config=/path/to/your/glib-config
     NOTE:      NOTE:
     In case you are using SHARED mime library, you may want to link in direct path to it,      In case you are using SHARED mime library, you may want to link in direct path to it,
     use this key to specify which linker key to use to do that:      use this key to specify which linker key to use do do that:
         --with-pathlink=LKEY    put dynamic libraries paths to binary          --with-pathlink=LKEY    put dynamic libraries paths to binary
                                 using linker key (-R, -rpath-link)                                  using linker key (-R, -rpath-link)
   
Line 150 Line 156
   and afterwards copy parser3install/bin/parser3 to your CGI directory    and afterwards copy parser3install/bin/parser3 to your CGI directory
   or make a symlink [if your web server configured to follow symlinks].    or make a symlink [if your web server configured to follow symlinks].
   
   You can disable libstdc++ linkage by setting  
   --disable-link-libstdcpp  
   option to configure.    
   
   You can disable any exec operations by setting    You can disable any exec operations by setting
   --disable-execs    --disable-execs
   option to configure.    option to configure.
Line 173 Line 175
   --with-sjlj-exceptions    --with-sjlj-exceptions
   option.      option.  
   
     By default libstdc++ is linked statically, you can re-enable dynamic libstdc++ linkage by specifying
     --with-dynamic-stdcpp
     option to configure.  
   
   
   Some root config options can be specified at configure time, and would override autodetects.    Some root config options can be specified at configure time, and would override autodetects.
   
   List of enabled charsets:    List of enabled charsets:
Removed from v.1.32  
changed lines
  Added in v.1.35

E-mail: