User Tools

Site Tools


en:user_advanced:installation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
en:user_advanced:installation [2019/05/29 09:02] – [Source Component] anupamaen:user_advanced:installation [2023/08/03 03:07] (current) – [Source Distribution] anupama
Line 1: Line 1:
-This page is up to date for 3.06 (5 November 2014)Much of it was checked again to be up to date after 3.08.+Updated on 30 Sep 2021, with changes that do not apply for Greenstone 3.10 and earlier. 
 +For instructions related to compiling GS3.10 from source distribution or with source component, or with source code from before September 2021, refer to the now [[old:user_advanced:installation|older version of this Advanced Installation page]]. 
  
 ====== Advanced Installation ====== ====== Advanced Installation ======
Line 17: Line 19:
  
  
-  * [[en:developer:compiling_greenstone|Compiling Greenstone]]+  * [[en:developer:compiling_greenstone2|Compiling Greenstone2]] 
 +  * [[en:developer:compiling_greenstone3|Compiling Greenstone3]] 
  
 +**Important Note:** Before proceeding, you're to set all instructed environment variables in the same terminal, unless explicitly stated otherwise.
  
 ===== Windows ===== ===== Windows =====
  
 Prerequisites for compiling the source component and source distribution on Windows: Prerequisites for compiling the source component and source distribution on Windows:
-  * Java JDK 6.x or later. For compiling on Windows 64 bit, need the 64 bit version of JDK. For compiling Greenstone 3.06 and onwards, need JDK 7.x or later.+  * For compiling on Windows 64 bit, need the 64 bit version of JDK. For 3.11 and onwards, JDK 8 is needed. For compiling Greenstone 3.06 and onwards, need JDK 7.x or later. For old versions of Greenstone: Java JDK 6.x or later. 
 +C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Auxiliary\Build\vcvarsall.bat
   * PERL: if you're using GS3.07 or earlier, get ActivePerl for Windows. From GS3.08 onwards, binaries and source distributions come with a [[http://trac.greenstone.org/browser/main/trunk/release-kits/shared/windows/perl.zip|Strawberry Perl]] located in the GS3's ''gs2build\bin\windows\perl'' folder.   * PERL: if you're using GS3.07 or earlier, get ActivePerl for Windows. From GS3.08 onwards, binaries and source distributions come with a [[http://trac.greenstone.org/browser/main/trunk/release-kits/shared/windows/perl.zip|Strawberry Perl]] located in the GS3's ''gs2build\bin\windows\perl'' folder.
   * Visual Studio 8 or later (Visual Studio 12 on 64 bit Windows 10 worked too.)   * Visual Studio 8 or later (Visual Studio 12 on 64 bit Windows 10 worked too.)
Line 41: Line 47:
 :: For this, need to cd into the folder where this script lives using the short filename path to this folder :: For this, need to cd into the folder where this script lives using the short filename path to this folder
 :: %0 is this script :: %0 is this script
-:: %~dp gives the full path to the folder containing this script. +:: For the following 2 lines, the spaces between percent sign, tilde and what follows after need to be removed 
-:: %~s gives the windows short filename version+:: when writing the active command based on those lines. Spaces have been inserted in the following 
 +:: to prevent this script from causing errors about these commented out lines when running. 
 +:: % ~ dp gives the full path to the folder containing this script. 
 +:: % ~ s gives the windows short filename version
 :: Combine to get what we want. :: Combine to get what we want.
 :: Note that this will leave the DOS prompt pointing to short filename of the folder :: Note that this will leave the DOS prompt pointing to short filename of the folder
Line 74: Line 83:
 :: (It may be apache httpd that needs 32 bit mode to compile.) :: (It may be apache httpd that needs 32 bit mode to compile.)
 :: For now only VS9.0 (VS2008) works :: For now only VS9.0 (VS2008) works
 +
  
 :: FOR COMPILING GS2 on WINDOWS: :: FOR COMPILING GS2 on WINDOWS:
Line 85: Line 95:
 :: (if using 64 bit windows, uncomment the following line by removing the two colons at its start) :: (if using 64 bit windows, uncomment the following line by removing the two colons at its start)
 :: call "C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\vcvarsall.bat" amd64 :: call "C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\vcvarsall.bat" amd64
 +
 +
 +
 +:: TO LOCATE YOUR vcvars32.bat (GS2/GS3) OR vcvarsall.bat (GS3) IN YOUR VISUAL STUDIO INSTALLATION:
 +:: Different Visual Studio installations can contain the vcvars32.bat and/or vcvarsall.bat in locations
 +:: different to the above examples. To locate your installation's instances of these scripts:
 +:: Open a DOS prompt and cd/change directory into your Visual Studio folder. Then use the command: dir /b /s "*search-term*"
 +:: and specify find the vcvars script by name, e.g.
 +:: C:\Program Files (x86)\Microsoft Visual Studio>dir /b /s "*vcvarsall.bat*"
 +:: If such a file exists within your Visual Studio installation, the prompt will return the location, e.g.
 +::    C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Auxiliary\Build\vcvarsall.bat
 +:: Use this result in the "call" command above
 +:: (and further, only for vcvarsall.bat, but not for vcvars32.bat, pass in: amd64), e.g.
 +:: call "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Auxiliary\Build\vcvarsall.bat" amd64
 +
  
 :done :done
Line 90: Line 115:
 To make it easier for developers, a batch file containing placeholders you can adjust is already prepared and discussed at [[http://wiki.greenstone.org/doku.php?id=en:developer:windows_source_install|Source Installation on Windows]]. To make it easier for developers, a batch file containing placeholders you can adjust is already prepared and discussed at [[http://wiki.greenstone.org/doku.php?id=en:developer:windows_source_install|Source Installation on Windows]].
 ==== Source Component ==== ==== Source Component ====
-<TABAREA tabs="Greenstone3,Greenstone2"> +<tabbox Greenstone3> 
-<TAB+**Note:** Greenstone 3 does not at present compile successfully if it was installed in a place containing spaces. The solution is to move the installed GS3 folder out into a different location, one without spaces in the filepath, //before// compiling. Once compiling is done, you can move your installed GS3 folder back to its original location.
-**Note:** Greenstone 3 does not at present compile successfully if it was installed in a place containing spaces. The solution is to move the installed folder out into a different location before compiling so that its install filepath does not contain spaces. Once compiling is done, you can move it back to its original location.+
  
   - Get the source component zip file from the downloads page.   - Get the source component zip file from the downloads page.
Line 101: Line 125:
   - The Java Runtime (JRE) included with Greenstone 3 binaries is a 32 bit Java 7 runtime. This means that //if the Windows machine that you're recompiling the binary with the source component on is not 32 bit Java 7 too//, then you will need to do the following before compiling \\   - The Java Runtime (JRE) included with Greenstone 3 binaries is a 32 bit Java 7 runtime. This means that //if the Windows machine that you're recompiling the binary with the source component on is not 32 bit Java 7 too//, then you will need to do the following before compiling \\
      * rename ''packages\jre'' to something else, so that when Greenstone runs after compiling, it uses your system Java rather than the old 32 bit JRE v7.      * rename ''packages\jre'' to something else, so that when Greenstone runs after compiling, it uses your system Java rather than the old 32 bit JRE v7.
-     * run ''ant distclean'' from the toplevel Greenstone installation folder, to clear all the older compile products created by compiling with 32 bit Java 7.+     * run ''ant distclean'' from the toplevel Greenstone installation folder, to clear all the older compile products created by compiling with 32 bit Java 7.\\ If you see the following error message <code>     [exec] Could Not Find GS3\gs2build\common-src\src\gdbmedit\gdbmdel\*.obj 
 +     [exec] Could Not Find GS3\gs2build\common-src\src\gdbmedit\gdbmdel\gdbmdel.exe 
 +     [exec]     cd "GS3\gs2build\common-src" 
 +     [exec]     cd src\gdbmedit\gdbmdel 
 +     [exec]     "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Tools\MSVC\14.11.25503\bin\HostX64\x6 
 +4\nmake.exe" /f win32.mak GSDLHOME="GS3\gs2build" clean 
 +     [exec]     del *.obj 
 +     [exec]     del gdbmdel.exe 
 +     [exec]     cd "GS3\gs2build\common-src" 
 +     [exec]     cd indexers 
 +     [exec]     set DEBUG=0 
 +     [exec]     set VISUAL_STUDIO_MAJORVERSION= 
 +     [exec]     set ENABLE_MG=1 
 +     [exec]     set ENABLE_MGPP=1 
 +     [exec]     set ENABLE_LUCENE=1 
 +     [exec]     call winMake.bat clean 
 +     [exec] GS3\gs2build\common-src\indexers\bin\*, Are you sure (Y/N)? 
 +>>>>     [exec] 14 was unexpected at this time. <<<<<<<<<<<<<<<<<<<< 
 +     [exec] NMAKE : fatal error U1077: 'call' : return code '0xff' 
 +     [exec] Stop. 
 + 
 +BUILD FAILED 
 +GS3\build.xml:4104: exec returned: 2</code>Edit your GS3\gs2build\common-src\indexers\winMake.bat script by commenting out the following line in it<code>::if %VISUAL_STUDIO_MAJORVERSION% LSS 14 set ICONVZIP=iconv-PRE-VS14.zip</code>\\ If you see a failure message about being unable to delete a file called 'cp.jar', run ''del \path\to\cp.jar'' manually from the command line for the exact file path listed. Then re-run ''ant distclean''. There are several cp.jar files in different locations of the GS3 installation, any or all of which can cause this failure message. So keep repeating the cycle of re-running ''ant distclean'' then manually running ''del'' on any cp.jar file listed in any failure message, until the ''ant distclean'' step finally succeeds (so without failure messages). This issue may be due to Windows having filelocks on the ''cp.jar'' files.
      * you may also want to want to delete ''gli\jar'' and ''gli\classes\org'', if they exist, to clear up GLI before recompiling.           * you may also want to want to delete ''gli\jar'' and ''gli\classes\org'', if they exist, to clear up GLI before recompiling.     
   - Finally, you can compile Greenstone 3. Still in your Greenstone installation folder, run ''ant install''.   - Finally, you can compile Greenstone 3. Still in your Greenstone installation folder, run ''ant install''.
  
-**Note for Windows 64 bit:**+**To run GS3 after re-compiling:**
  
-To run GLI after recompiling your binary on a 64 bit Windows machine, you need JDK 7 (or JRE 7) for 64 bit set up in your environmentsince the JRE included with the Greenstone Windows binary is for 32 bitas the Greenstone Windows binary itself is 32 bitOtherwise, the problem seen when running the 64-bit recompiled GS3 server with the 32-bit JRE included in GS3 binaries is a tomcat error explaining the discrepancy between the two architectures.+To run GLI after recompiling your binary on a 64 bit Windows machine, you need the same version of JDK or JRE (and for the same bit architecture, 32 or 64 bitas that you used to compile up Greenstone 3You will need this Java's ''bin'' subfolder on your PATH. You'll also need the ''bin'' subfolder of ANT on the PATH.
  
-Therefore, to run GLI after compiling GS3 for 64 bit, add the bin folder of JRE for 64 bit to the PATH, or set JAVA_HOME to JDK 64 bit and add its bin folder to the PATH. Then run GLI in this environment. +**Note if you want to use the bundled JRE for Windows 64 bit:** 
-</TAB> + 
-<TAB>+To run GLI after recompiling your binary on a 64 bit Windows machine, you need JDK 8 or JRE 8 (for pre-GS3.11 you'd need JDK 7 else JRE 7) for 64 bit set up in your environment, since the JRE included with the Greenstone Windows binary is for 32 bit, as the Greenstone Windows binary itself is 32 bit. Otherwise, the problem seen when running the 64-bit recompiled GS3 server with the 32-bit JRE included in GS3 binaries is a tomcat error explaining the discrepancy between the two architectures. 
 + 
 +Therefore, to run GLI after compiling GS3 for 64 bit, add the bin folder of JRE for 64 bit to the PATH, or set JAVA_HOME to JDK 64 bit and add its bin folder to the PATH. Then run GLI in this environment. 
 +<tabbox Greenstone2>
   - Get the source component zip file from the downloads page.   - Get the source component zip file from the downloads page.
   - Unzip it in your Greenstone installation. If Windows prompts you about whether you want existing folders merged (and existing files replaced), tick the box to confirm for all and click in the affirmative.   - Unzip it in your Greenstone installation. If Windows prompts you about whether you want existing folders merged (and existing files replaced), tick the box to confirm for all and click in the affirmative.
Line 125: Line 174:
  
 **Note:** Building collections that use lucene as their indexer requires Java. If you compiled up GS2 using a later version of Java than the version of JRE included in the binary (Java 7), then building a lucene collection may produce error messages about incompatible java versions. In such a case, rename your GS2 installation ''packages/jre'' subfolder so that Greenstone no longer finds the bundled JRE. Before re-running GLI to rebuild your lucene collection, ensure that the Java you compiled GS2 with is in the environment (so that JAVA_HOME set to it and its ''bin'' folder is on the PATH). Remember to use the same Java environment to launch this GS2 installation's applications in future. **Note:** Building collections that use lucene as their indexer requires Java. If you compiled up GS2 using a later version of Java than the version of JRE included in the binary (Java 7), then building a lucene collection may produce error messages about incompatible java versions. In such a case, rename your GS2 installation ''packages/jre'' subfolder so that Greenstone no longer finds the bundled JRE. Before re-running GLI to rebuild your lucene collection, ensure that the Java you compiled GS2 with is in the environment (so that JAVA_HOME set to it and its ''bin'' folder is on the PATH). Remember to use the same Java environment to launch this GS2 installation's applications in future.
-</TAB> +</tabbox>
-</TABAREA>+
 ==== Source Distribution ==== ==== Source Distribution ====
-<TABAREA tabs="Greenstone3,Greenstone2"> +<tabbox Greenstone3>
-<TAB>+
   - Get the source distribution zip file from the downloads page.   - Get the source distribution zip file from the downloads page.
   - //Unzip it in a location with no spaces in the filepath.//   - //Unzip it in a location with no spaces in the filepath.//
Line 135: Line 182:
   - Set up the environment for compiling Greenstone by running the setupenv.bat script described above: ''setupenv.bat''. (For 64-bit Windows, make sure the script sets JAVA_HOME to a 64-bit JDK7, and adds its ''bin'' folder to the PATH, and that the script then calls ''vsvarsall.bat amd64'' of your Visual Studio. VS Version 9 has been tested to work.)   - Set up the environment for compiling Greenstone by running the setupenv.bat script described above: ''setupenv.bat''. (For 64-bit Windows, make sure the script sets JAVA_HOME to a 64-bit JDK7, and adds its ''bin'' folder to the PATH, and that the script then calls ''vsvarsall.bat amd64'' of your Visual Studio. VS Version 9 has been tested to work.)
   - Go into your Greenstone 3 installation folder, ''cd C:\path\to\Greenstone3\'', and run ''gs3-setup.bat''.   - Go into your Greenstone 3 installation folder, ''cd C:\path\to\Greenstone3\'', and run ''gs3-setup.bat''.
 +  - Edit your ''GS3\gs2build\common-src\indexers\winMake.bat'' script by commenting out the following line in it by prefixing 2 colon signs (''::'') to the line<code>if %VISUAL_STUDIO_MAJORVERSION% LSS 14 set ICONVZIP=iconv-PRE-VS14.zip</code>So it looks as follows, then save the script file:<code>::if %VISUAL_STUDIO_MAJORVERSION% LSS 14 set ICONVZIP=iconv-PRE-VS14.zip</code>
   - Now you can finally compile Greenstone 3. Still in your Greenstone installation folder, run ''ant install''.   - Now you can finally compile Greenstone 3. Still in your Greenstone installation folder, run ''ant install''.
   - It can take several minutes to compile up.   - It can take several minutes to compile up.
 +  - If you don't already have an imagemagick installed on your system and want to have //imagemagick// in your GS installation, as imagemagick is used to create thumbnail and screenview size images from your full size images, then grab the pre-compiled imagemagick Windows binary from http://trac.greenstone.org/export/head/gs2-extensions/imagemagick/trunk/imagemagick-windows.zip and unzip it into your compiled up GS3 source distribution folder's ''gs2build\bin\windows'' subfolder, so that you end up with an ''imagemagick'' folder in there. Make sure it hasn't created an extra level of an ''imagemagick'' subfolder on extraction, like ''gs2build\bin\windows\imagemagick\imagemagick''. (The dll files should be at the ''gs2build\bin\windows\imagemagick'' level.)
 +
  
 **Notes for Windows 64 bit:** **Notes for Windows 64 bit:**
  
-To run GLI or the gs3-server after compiling the source code on a 64 bit Windows machine, you need your environment to be set up with JDK 7+ (or JRE 7+) for 64-bit and Ant: set the JAVA_HOME environment variable to your 64 bit JDK and add the JDK's ''bin'' folder to the PATH. Also set the ANT_HOME environment variable and add its ''bin'' folder to the PATH. Then run GLI or gs2-server in this environment using the gli.bat and gs2-server.bat scripts.  +To run GLI or the gs3-server after compiling the source code on a 64 bit Windows machine, you need your environment to be set up with JDK 8 or JRE 8 (or JDK 7+ else JRE 7+ for Greenstone versions prior to GS3.11) for 64-bit and Ant: set the JAVA_HOME environment variable to your 64 bit JDK and add the JDK's ''bin'' folder to the PATH. Also set the ANT_HOME environment variable and add its ''bin'' folder to the PATH. Then run GLI or gs2-server in this environment using the gli.bat and gs2-server.bat scripts.  
-</TAB> +<tabbox Greenstone2>
-<TAB>+
   - Get the source distribution zip file from the downloads page.   - Get the source distribution zip file from the downloads page.
   - Unzip it   - Unzip it
Line 155: Line 204:
   - If you wish to compile up the GLI jar files, such as for Remote Greenstone situations, run the following from within the gli folder: ''makejar.bat''.   - If you wish to compile up the GLI jar files, such as for Remote Greenstone situations, run the following from within the gli folder: ''makejar.bat''.
   - You will need to enable the Administration pages if you want access to them. Do so by editing your Greenstone installation's ''etc/main.cfg'' file. Change the ''status'' field value from ''disabled'' to ''enabled''. In that case, you may also want to change the admin password for the Adminstration pages. Use a DOS prompt to run: ''gsicontrol.bat configure-admin'' which will allow you to (re)set the password for username ''admin'' (the default admin password is the same as the username).   - You will need to enable the Administration pages if you want access to them. Do so by editing your Greenstone installation's ''etc/main.cfg'' file. Change the ''status'' field value from ''disabled'' to ''enabled''. In that case, you may also want to change the admin password for the Adminstration pages. Use a DOS prompt to run: ''gsicontrol.bat configure-admin'' which will allow you to (re)set the password for username ''admin'' (the default admin password is the same as the username).
-  - If you don't already have an imagemagick installed and want to have //imagemagick// in your GS installation, as imagemagick is used to create thumbnail and screenview size images from your full size images, then grab the pre-compiled imagemagick Windows binary from http://trac.greenstone.org/export/head/gs2-extensions/imagemagick/trunk/imagemagick-windows.zip and unzip it into your compiled up GS2 source distribution folder's ''bin\windows'' subfolder, so that you end up with an ''imagemagick'' folder in there. Make sure it hasn't created an extra level of an ''imagemagick'' subfolder on extraction, like ''bin\windows\imagemagick\imagemagick''. (The dll files should be at the ''bin\windows\imagemagick'' level.) +  - If you don't already have an imagemagick installed on your system and want to have //imagemagick// in your GS installation, as imagemagick is used to create thumbnail and screenview size images from your full size images, then grab the pre-compiled imagemagick Windows binary from http://trac.greenstone.org/export/head/gs2-extensions/imagemagick/trunk/imagemagick-windows.zip and unzip it into your compiled up GS2 source distribution folder's ''bin\windows'' subfolder, so that you end up with an ''imagemagick'' folder in there. Make sure it hasn't created an extra level of an ''imagemagick'' subfolder on extraction, like ''bin\windows\imagemagick\imagemagick''. (The dll files should be at the ''bin\windows\imagemagick'' level.) 
-</TAB> +</tabbox>
-</TABAREA>+
  
  
Line 163: Line 211:
  
 Prerequisites for compiling on Windows: Prerequisites for compiling on Windows:
-  * Java JDK 6.x or later+  * Java JDK 6.x or later, JDK 7+ for GS3.06 onwards, and JDK 8 for GS3.11 onwards
   * PERL (ActivePerl for Windows   * PERL (ActivePerl for Windows
   * Visual Studio 8 or later   * Visual Studio 8 or later
Line 176: Line 224:
 which can be accomplished using the file ''vcvars<number>.bat'', or ''vcvarsall.bat'' passing in ''amd64'' for 64 bit windows. which can be accomplished using the file ''vcvars<number>.bat'', or ''vcvarsall.bat'' passing in ''amd64'' for 64 bit windows.
  
-<TABAREA tabs="Greenstone3,Greenstone2"> +<tabbox Greenstone3>
-<TAB>+
 Run the following: Run the following:
 <code> <code>
-svn co http://svn.greenstone.org/main/trunk/greenstone3+svn co https://svn.greenstone.org/main/trunk/greenstone3 gs3-svn 
 +cd gs3-svn
 ant ant
 ant prepare ant prepare
 ant install ant install
 </code> </code>
-</TAB+<tabbox Greenstone2
-<TAB+<code> 
-Then run:+svn co https://svn.greenstone.org/main/trunk/greenstone2 gs2-svn 
 +cd gs2-svn 
 +</code
 +Then on 64 bit Windows run: 
 +<code> 
 +makegs2x64.bat 
 +</code> 
 +whereas on 32 bit Windows, you'd need to run:
 <code> <code>
 makegs2.bat makegs2.bat
Line 193: Line 248:
   * Choose yes twice   * Choose yes twice
   * Choose step 4 to compile ALL without debugging   * Choose step 4 to compile ALL without debugging
-</TAB+ 
-</TABAREA>+Check out and compile GLI: 
 +<code> 
 +svn co https://svn.greenstone.org/main/trunk/gli 
 +cd gli 
 +makegli.bat 
 +makejar.bat 
 +</code
 +</tabbox>
  
 For more detailed instructions on source installation, please refer to the  For more detailed instructions on source installation, please refer to the 
Line 208: Line 270:
  
 ==== Source Component ==== ==== Source Component ====
-<TABAREA tabs="Greenstone3,Greenstone2"> +<tabbox Greenstone3>
-<TAB>+
   - Download and extract the Source Component for your Operating System into the top-level folder of your Greenstone 3 binary installation. For Linux/Mac, download the tar.gz version as zip doesn't preserve necessary file permissions.   - Download and extract the Source Component for your Operating System into the top-level folder of your Greenstone 3 binary installation. For Linux/Mac, download the tar.gz version as zip doesn't preserve necessary file permissions.
-  - Set up ant and Java: set JAVA_HOME (to JDK 7 for Greenstone 3.06) and add its ''bin'' folder to the PATH. If you're on a 64 bit machine, you'll need a JDK for 64 bit machines, if you're on a 32 bit machine, you will need a JDK for 32 bit machines. Set ANT_HOME and add its ''bin'' folder to the PATH. If you don't already have ant installed, the Greenstone 3 binary comes with one in its ''packages/ant'' folder. Set that to ANT_HOME, and add its ''bin'' subfolder to the PATH.\\ <code>+  - Set up ant and Java: set JAVA_HOME (to JDK 7 for Greenstone 3.06, JDK 8 for Greenstone 3.11 onwards) and add its ''bin'' folder to the PATH. If you're on a 64 bit machine, you'll need a JDK for 64 bit machines, if you're on a 32 bit machine, you will need a JDK for 32 bit machines. Set ANT_HOME and add its ''bin'' folder to the PATH. If you don't already have ant installed, the Greenstone 3 binary comes with one in its ''packages/ant'' folder. Set that to ANT_HOME, and add its ''bin'' subfolder to the PATH.\\ <code>
 export JAVA_HOME=/path/to/your/jdk7 export JAVA_HOME=/path/to/your/jdk7
 export ANT_HOME=/path/to/GS3/packages/ant export ANT_HOME=/path/to/GS3/packages/ant
 export PATH=$JAVA_HOME/bin:$ANT_HOME/bin:$PATH export PATH=$JAVA_HOME/bin:$ANT_HOME/bin:$PATH
-</code>If you're on Mac OS version 10.11/El Capitan, set CFLAGS, CXXFLAGS and JNIFLAGS as follows: \\ <code>export CFLAGS="$CFLAGS -I$JAVA_HOME/include -I$JAVA_HOME/include/darwin"+</code>**If you're on Mac OS version anywhere from 10.11/El Capitan until Mojava (and possibly Catalina)**, set CFLAGS, CXXFLAGS and JNIFLAGS as follows: \\ <code>export CFLAGS="$CFLAGS -I$JAVA_HOME/include -I$JAVA_HOME/include/darwin"
 export CXXFLAGS="$CXXFLAGS $CFLAGS" export CXXFLAGS="$CXXFLAGS $CFLAGS"
-export JNICFLAGS="$JNICFLAGS $CFLAGS"</code> Since GS3.08, if you're on 64 bit linux, you will also need to add -fPIC to the CFLAGS and CXXFLAGS environment variables: \\ <code>export CFLAGS="-fPIC $CFLAGS"+export JNICFLAGS="$JNICFLAGS $CFLAGS"</code> **Since GS3.08 and until GS3.10**, if you're on 64 bit linux, you will also need to add -fPIC to the CFLAGS and CXXFLAGS environment variables: \\ <code>export CFLAGS="-fPIC $CFLAGS"
 export CXXFLAGS="-fPIC $CXXFLAGS"</code>If at any point you run ''source ./gs3-setup.sh'' before compiling, you will have to set up the Java JDK environment again, because the ''gs3-setup'' script will make the included JRE the default Java. export CXXFLAGS="-fPIC $CXXFLAGS"</code>If at any point you run ''source ./gs3-setup.sh'' before compiling, you will have to set up the Java JDK environment again, because the ''gs3-setup'' script will make the included JRE the default Java.
-  - The Java Runtime (JRE) included in binaries from Greenstone 3.07 onward is version 7. For 32 bit linux binaries, the included JRE is 32 bit and for 64 bit linux binaries the JRE is 64 bit. //If you have set up a system Java of a version different from the JRE included//, then \\+  - The Java Runtime (JRE) included in binaries from Greenstone 3.07 onward is version 7 and version 8 for Greenstone 3.11 onward. For 32 bit linux binaries, the included JRE is 32 bit and for 64 bit linux binaries the JRE is 64 bit. //If you have set up a system Java of a version different from the JRE included//, then \\
      * rename the ''packages\jre'' folder to something else, so that when Greenstone runs after compiling, it uses your system Java rather than the old 32 bit JRE v7.      * rename the ''packages\jre'' folder to something else, so that when Greenstone runs after compiling, it uses your system Java rather than the old 32 bit JRE v7.
      * run ''ant distclean'' from the toplevel Greenstone installation folder, to clear all the older compile products that were compiled with Java 7.      * run ''ant distclean'' from the toplevel Greenstone installation folder, to clear all the older compile products that were compiled with Java 7.
Line 231: Line 292:
 cd ../../.. cd ../../..
 </code> </code>
-  - In the terminal, you can now finally run ''ant install'' //from the toplevel folder// of the Greenstone 3 installation to start compiling. It can take several minutes. \\ **Note:** If at this stage, compilation fails at Perl's XMLParser with [[http://gentoo.2317880.n4.nabble.com/PREFIX-revolutions-in-the-bootstrapping-world-td181438.html|the error message]] "Only one of PREFIX or INSTALL_BASE can be given. Not both.", then in the same terminal check if the INSTALL_BASE environment variable is set, and if it is, unset it (and PERL_MM_OPT if it was set to this) and re-run ''ant install'':\\ <code>+  - In the same terminal, you can now finally run ''ant install'' //from the toplevel folder// of the Greenstone 3 installation to start compiling. It can take several minutes. \\ **Note:** If at this stage, compilation fails at Perl's XMLParser with [[http://gentoo.2317880.n4.nabble.com/PREFIX-revolutions-in-the-bootstrapping-world-td181438.html|the error message]] "Only one of PREFIX or INSTALL_BASE can be given. Not both.", then in the same terminal check if the INSTALL_BASE environment variable is set, and if it is, unset it (and PERL_MM_OPT if it was set to this) and re-run ''ant install'':\\ <code>
 > env | grep INSTALL > env | grep INSTALL
 PERL_MM_OPT=INSTALL_BASE=/something.../ PERL_MM_OPT=INSTALL_BASE=/something.../
Line 242: Line 303:
  
 The gnome-lib environment may conflict with graphical applications on Linux systems. After compiling, open a fresh terminal to run GLI or other graphical applications. But make sure the new terminal has the environment set up for Java and Ant too before running any Greenstone applications like the Greenstone Server (gs3-server) and GLI. The gnome-lib environment may conflict with graphical applications on Linux systems. After compiling, open a fresh terminal to run GLI or other graphical applications. But make sure the new terminal has the environment set up for Java and Ant too before running any Greenstone applications like the Greenstone Server (gs3-server) and GLI.
-</TAB> + 
-<!-- ############# --> + 
-<TAB>+<tabbox Greenstone2>
   - Download the Source Component tar.gz file that matches with your Greenstone binary version, and put it in your Greenstone installation folder. For Linux/Mac, you want the tar.gz version because the zip version doesn't preserve necessary file permissions.   - Download the Source Component tar.gz file that matches with your Greenstone binary version, and put it in your Greenstone installation folder. For Linux/Mac, you want the tar.gz version because the zip version doesn't preserve necessary file permissions.
   - Use a terminal to extract the downloaded file's contents into your Greenstone installation folder: \\ <code>cd <your greenstone folder>   - Use a terminal to extract the downloaded file's contents into your Greenstone installation folder: \\ <code>cd <your greenstone folder>
Line 320: Line 381:
  
 where the WebServerName and WebServerPort are what you specified when you [[en:user_advanced:gs2_server| set up your web server]].  where the WebServerName and WebServerPort are what you specified when you [[en:user_advanced:gs2_server| set up your web server]]. 
-</TAB> +</tabbox>
-</TABAREA>+
 ==== Source Distribution ==== ==== Source Distribution ====
  
Line 338: Line 398:
 </code> </code>
  
-<TABAREA tabs="Greenstone3,Greenstone2"> +<tabbox Greenstone3>
-<TAB>+
   - Download the Source Distribution for your Operating System and extract it into the location where you want Greenstone installed. For Linux/Mac, download the tar.gz version as zip doesn't preserve necessary file permissions.   - Download the Source Distribution for your Operating System and extract it into the location where you want Greenstone installed. For Linux/Mac, download the tar.gz version as zip doesn't preserve necessary file permissions.
-  - Make sure JAVA_HOME is set (to JDK 7 for Greenstone 3.06) and that its ''bin'' folder is added to the PATH. If you're on a 64 bit machine you need a JDK for 64 bit machines, if you're on a 32 bit machine, you will need a JDK for 32 bit machines. Also set ANT_HOME to an ant installation and add its ''bin'' folder to the PATH.+  - Make sure JAVA_HOME is set (to JDK 7 for Greenstone 3.06, JDK 8 from Greenstone 3.11 onwards) and that its ''bin'' folder is added to the PATH. If you're on a 64 bit machine you need a JDK for 64 bit machines, if you're on a 32 bit machine, you will need a JDK for 32 bit machines. Also set ANT_HOME to an ant installation and add its ''bin'' folder to the PATH.
   - Most of the linux and mac machines we tested require the gnome-lib extension. Without it, if compiling fails with an error message about ''wvware'', then it means you need the gnome-lib extension. You can grab it by visiting http://trac.greenstone.org/browser/gs2-extensions/gnome-lib/trunk, selecting the link to the ''gnome-lib-minimal'' version for your operating system and architecture, then clicking on the download link on the subsequent page. Download it into your extracted Greenstone 3's ''gs2build/ext'' folder.   - Most of the linux and mac machines we tested require the gnome-lib extension. Without it, if compiling fails with an error message about ''wvware'', then it means you need the gnome-lib extension. You can grab it by visiting http://trac.greenstone.org/browser/gs2-extensions/gnome-lib/trunk, selecting the link to the ''gnome-lib-minimal'' version for your operating system and architecture, then clicking on the download link on the subsequent page. Download it into your extracted Greenstone 3's ''gs2build/ext'' folder.
   - Use the terminal to extract the downloaded gnome-lib-minimal extension and set up the gnome-lib environment for compiling as follows:\\ <code>   - Use the terminal to extract the downloaded gnome-lib-minimal extension and set up the gnome-lib environment for compiling as follows:\\ <code>
 cd gs2build/ext cd gs2build/ext
-tar -xvzf gnome-lib-minimal-<your-OS-version>.tar.gz +cd gnome-lib  
-cd gnome-lib-minimal+# gnome-lib can take longer to compile.  
 +# Alternatively, if you had internet access and had grabbed the gnome-lib-minimal tarball 
 +# as per instructions above, then run the following commands:  
 +#mv gnome-lib gnome-lib.orig 
 +#tar -xvzf gnome-lib-minimal-<your-OS-version>.tar.gz  
 +#cd gnome-lib-minimal
 source ./devel.bash source ./devel.bash
 cd ../../.. cd ../../..
 </code> </code>
-  - If you're on Mac OS version 10.11/El Capitan, set CFLAGS, CXXFLAGS and JNIFLAGS as follows: \\ <code>export CFLAGS="$CFLAGS -I$JAVA_HOME/include -I$JAVA_HOME/include/darwin"+  - **If you're on Mac OS version anywhere from 10.11/El Capitan until Mojava (and possibly Catalina)**, set CFLAGS, CXXFLAGS and JNIFLAGS as follows: \\ <code>export CFLAGS="$CFLAGS -I$JAVA_HOME/include -I$JAVA_HOME/include/darwin"
 export CXXFLAGS="$CXXFLAGS $CFLAGS" export CXXFLAGS="$CXXFLAGS $CFLAGS"
-export JNICFLAGS="$JNICFLAGS $CFLAGS"</code> Since GS3.08, if you're on 64 bit linux, you will also need to add -fPIC to the CFLAGS and CXXFLAGS environment variables: \\ <code>export CFLAGS="-fPIC $CFLAGS"+export JNICFLAGS="$JNICFLAGS $CFLAGS"</code> **Since GS3.08 and upto and including GS3.10**, if you're on 64 bit linux, you will also need to add -fPIC to the CFLAGS and CXXFLAGS environment variables: \\ <code>export CFLAGS="-fPIC $CFLAGS"
 export CXXFLAGS="-fPIC $CXXFLAGS"</code> export CXXFLAGS="-fPIC $CXXFLAGS"</code>
-  - In the terminal, you can now finally run ''ant install'' from //the toplevel folder// of your extracted Greenstone 3 installation to start compilation. It can take several minutes. \\ **Note:** If at this stage, compilation fails at Perl's XMLParser with [[http://gentoo.2317880.n4.nabble.com/PREFIX-revolutions-in-the-bootstrapping-world-td181438.html|the error message]] "Only one of PREFIX or INSTALL_BASE can be given. Not both.", then in the same terminal check if the INSTALL_BASE environment variable is set, and if it is, unset it (and PERL_MM_OPT if it was set to this) and re-run ''ant install'':\\ <code>+  - In the same terminal, you can now finally run ''ant install'' from //the toplevel folder// of your extracted Greenstone 3 installation to start compilation. It can take several minutes. \\ **Note:** If at this stage, compilation fails at Perl's XMLParser with [[http://gentoo.2317880.n4.nabble.com/PREFIX-revolutions-in-the-bootstrapping-world-td181438.html|the error message]] "Only one of PREFIX or INSTALL_BASE can be given. Not both.", then in the same terminal check if the INSTALL_BASE environment variable is set, and if it is, unset it (and PERL_MM_OPT if it was set to this) and re-run ''ant install'':\\ <code>
 > env | grep INSTALL > env | grep INSTALL
 PERL_MM_OPT=INSTALL_BASE=/something.../ PERL_MM_OPT=INSTALL_BASE=/something.../
Line 360: Line 424:
 > export PERL_MM_OPT= > export PERL_MM_OPT=
 > ant install</code> > ant install</code>
 +  - **For Mac OS, from El Capitan onwards:** If you don't already have an imagemagick installed on your system and want to have //imagemagick// in your GS installation, as imagemagick is used to create thumbnail and screenview size images from your full size images, then we found that the pre-compiled imagemagick binary at https://trac.greenstone.org/export/head/gs2-extensions/imagemagick/trunk/imagemagick-darwin-10.11.tar.gz, though built on Mac El Capitan, still works fine on Mac Monterey (Mac OS v 12.x). Grab it from that link and extract it. Then rename its ''darwin'' subfolder to ''imagemagick'' and move this subfolder into your GS3's ''gs2build/bin/darwin'' folder. Launching GLI now should find this imagemagick and use it to generate thumbnails and screenview images.
  
 **Note:** **Note:**
  
-The gnome-lib environment may conflict with graphical applications on Linux systems. After compiling, open a fresh terminal to run GLI or other graphical applications. Make sure the new terminal has the environment set up for Java and Ant too before running any Greenstone applications like the Greenstone Server (gs3-server) and GLI. +The gnome-lib environment may conflict with graphical applications on Linux systems. After compiling, open a fresh terminal to run GLI or other graphical applications. Make sure the new terminal has the environment set up for Java (version 8 from GS3.11 and onwards) and Ant too before running any Greenstone applications like the Greenstone Server (gs3-server) and GLI. 
-</TAB> + 
-<!-- ####################################################### --> +<tabbox Greenstone2>
-<TAB>+
   - Download the Source Distribution and extract it. For Linux/Mac, please use the tar.gz version as zip doesn't preserve necessary file permissions.   - Download the Source Distribution and extract it. For Linux/Mac, please use the tar.gz version as zip doesn't preserve necessary file permissions.
   - If you want to compile up gnome-lib yourself, skip this step. If you want to use a pre-compiled gnome-lib binary (to save on all the time of compiling gnome-lib), download the gnome-lib-minimal package for your OS by visiting http://trac.greenstone.org/browser/gs2-extensions/gnome-lib/trunk \\ Then unzip the downloaded gnome-lib minimal package into your greenstone2-home/ext    - If you want to compile up gnome-lib yourself, skip this step. If you want to use a pre-compiled gnome-lib binary (to save on all the time of compiling gnome-lib), download the gnome-lib-minimal package for your OS by visiting http://trac.greenstone.org/browser/gs2-extensions/gnome-lib/trunk \\ Then unzip the downloaded gnome-lib minimal package into your greenstone2-home/ext 
Line 378: Line 442:
   - You will need to enable the Administration pages if you want access to them. Do so by editing your Greenstone installation's ''etc/main.cfg'' file. Change the ''status'' field value from ''disabled'' to ''enabled''. In that case, you may also want to change the admin password for the Adminstration pages. Use a DOS prompt to run: ''gsicontrol.bat configure-admin'' which will allow you to (re)set the password for username ''admin'' (the default admin password is the same as the username).   - You will need to enable the Administration pages if you want access to them. Do so by editing your Greenstone installation's ''etc/main.cfg'' file. Change the ''status'' field value from ''disabled'' to ''enabled''. In that case, you may also want to change the admin password for the Adminstration pages. Use a DOS prompt to run: ''gsicontrol.bat configure-admin'' which will allow you to (re)set the password for username ''admin'' (the default admin password is the same as the username).
  
-</TAB> +</tabbox>
-</TABAREA>+
 ==== Uptodate source code from SVN ==== ==== Uptodate source code from SVN ====
  
-<TABAREA tabs="Greenstone3,Greenstone2"> +<tabbox Greenstone3>
-<TAB>+
  
   - Make sure you have SVN installed and on your Path   - Make sure you have SVN installed and on your Path
Line 390: Line 452:
 export ANT_HOME=/path/to/your/ant export ANT_HOME=/path/to/your/ant
 export PATH=$JAVA_HOME/bin:$ANT_HOME/bin:$PATH export PATH=$JAVA_HOME/bin:$ANT_HOME/bin:$PATH
-</code>+</code>\\ **NOTE:** Some of the prerequisite packages are available from greenstone's svn and are put into a subfolder called ''local''. For instructions on compiling up from source using the ''local'' folder, refer to the [[http://wiki.greenstone.org/doku.php?id=en:developer:unix_source_install|Unix source installation page]]. Otherwise, proceed with the following.
   - Checkout the code: <code>   - Checkout the code: <code>
-svn co http://svn.greenstone.org/main/trunk/greenstone3+svn co https://svn.greenstone.org/main/trunk/greenstone3
 </code> </code>
   - Generate the file ''build.properties'' with: <code>   - Generate the file ''build.properties'' with: <code>
 ant  ant 
 </code>\\ Now, if necessary, you can customise the port/hostname fields in the newly generated toplevel file ''build.properties''. </code>\\ Now, if necessary, you can customise the port/hostname fields in the newly generated toplevel file ''build.properties''.
-  - Most Linux systems and probably all the newer Mac systems require //gnome-lib// for successful compilation. If you wish to //compile gnome-lib// along with GS3, uncomment the following line in ''build.properties'' to activate it <code> +  - Most Linux systems and probably all the newer Mac systems require //gnome-lib// for successful compilation. This will compile gnome-lib along with GS3.\\ If you don't want to //compile// the gnome-lib extension when compiling GS3, but **prefer to use a pre-compiled ''gnome-lib''** to speed up the process, in which case you'll carry out step 9 later, **comment out** the following line (by prefixing a # symbol to the line) in ''build.properties'' to de-activate it: ''checkout.gnomelib.ext=true'' 
-checkout.gnomelib.ext=true +  - If you want to compile imagemagick from source on Unix systems (though for Mac you can also use the precompiled imagemagick binary*), uncomment the following line in ''build.properties'' to activate it <code>
-</code>\\ Skip this step if you don't want to //compile// the gnome-lib extension when compiling GS3, but prefer to use a pre-compiled ''gnome-lib'' to speed up the process, in which case you'll carry out step 9 later. +
-  - If you want to compile imagemagick from source on Unix systems (though for Mac you can also use the precompiled imagemagick binary*), <code>+
 checkout.imagemagick.ext=true checkout.imagemagick.ext=true
-</code>\\ **Not compiling at present on MacOS High Sierra (10.13.4).** So use the precompiled imagemagick binary* for that instead. +</code>\\ **imagemagick is not successfully compiling at present on MacOS High Sierra (10.13.4) onward (nor 32 bit linux at the moment).** So use the pre-compiled imagemagick binary* for Mac instead.  
-  - **If you're on Mac OS version 10.11/El Capitan or later**, set CFLAGS, CXXFLAGS and JNIFLAGS as follows: \\ <code>export CFLAGS="$CFLAGS -I$JAVA_HOME/include -I$JAVA_HOME/include/darwin" +
-export CXXFLAGS="$CXXFLAGS $CFLAGS" +
-export JNICFLAGS="$JNICFLAGS $CFLAGS"</code> Since GS3.08, **if you're on 64 bit linux**, you will need to add -fPIC to the CFLAGS and CXXFLAGS environment variables: \\ <code>export CFLAGS="-fPIC $CFLAGS" +
-export CXXFLAGS="-fPIC $CXXFLAGS"</code>+
   - Finally, you can start the steps for building GS3 from SVN: <code>   - Finally, you can start the steps for building GS3 from SVN: <code>
 ant prepare</code> ant prepare</code>
-  - This step is only applicable if you had decided on using a //pre-compiled// ''gnome-lib'' in step 5. In that case, visit http://trac.greenstone.org/browser/gs2-extensions/gnome-lib/trunk and there click on the link for the ''gnome-lib-**minimal**-'' zip/tarball for your operating system. On the next page, click on the download link to download the zip/tarball file, then move this downloaded file into ''gs2build/ext''. After that, unpack and set up your gnome-lib-minimal for compiling as follows: \\ <code>cd gs2build/ext+  - This step is only applicable if you had decided on using a //pre-compiled// ''gnome-lib'' in step 5. In that case, visit https://trac.greenstone.org/browser/gs2-extensions/gnome-lib/trunk and there click on the link for the ''gnome-lib-**minimal**-'' zip/tarball for your operating system. On the next page, click on the download link to download the zip/tarball file, then move this downloaded file into ''gs2build/ext''. After that, unpack and set up your gnome-lib-minimal for compiling as follows: \\ <code>cd gs2build/ext
 tar -xvzf gnome-lib-minimal-<your-OS-version>.tar.gz tar -xvzf gnome-lib-minimal-<your-OS-version>.tar.gz
 cd gnome-lib-minimal cd gnome-lib-minimal
Line 428: Line 484:
 <code> <code>
 cd gs2build cd gs2build
-svn co http://svn.greenstone.org/main/trunk/binaries/mac/intel/imagemagick bin/darwin/imagemagick +svn co https://svn.greenstone.org/main/trunk/binaries/mac/intel/ghostscript bin/darwin/ghostscript 
-svn co http://svn.greenstone.org/main/trunk/binaries/mac/intel/ghostscript bin/darwin/ghostscript+ 
 +svn export https://svn.greenstone.org/gs2-extensions/imagemagick/trunk/imagemagick-darwin-10.11.tar.gz 
 +tar -xvzf imagemagick-darwin-10.11.tar.gz 
 +mv imagemagick/darwin bin/darwin/imagemagick 
 +rm -rf imagemagick-darwin-10.11.tar.gz 
 +rm -rf imagemagick 
 </code> </code>
  
-</TAB> +<tabbox Greenstone2>
-<TAB>+
   - First grab all the source code from SVN by running the following commands in your terminal \\ <code>   - First grab all the source code from SVN by running the following commands in your terminal \\ <code>
-svn co http://svn.greenstone.org/main/trunk/greenstone2 greenstone2+svn co https://svn.greenstone.org/main/trunk/greenstone2 greenstone2
 cd greenstone2 cd greenstone2
-svn co http://svn.greenstone.org/main/trunk/gli+svn co https://svn.greenstone.org/main/trunk/gli
 </code> </code>
-  - If you want to compile up gnome-lib yourself, skip this step. If you want to use a pre-compiled gnome-lib binary, download the gnome-lib-minimal package for your OS by visiting http://trac.greenstone.org/browser/gs2-extensions/gnome-lib/trunk \\ Then unzip the downloaded gnome-lib minimal package into your greenstone2-home/ext +  - If you want to compile up gnome-lib yourself, skip this step. If you want to use a pre-compiled gnome-lib binary, download the gnome-lib-minimal package for your OS by visiting https://trac.greenstone.org/browser/gs2-extensions/gnome-lib/trunk \\ Then unzip the downloaded gnome-lib minimal package into your greenstone2-home/ext 
   - Compile up Greenstone: \\ <code>   - Compile up Greenstone: \\ <code>
 ./makegs2.sh gnome-lib ./makegs2.sh gnome-lib
Line 447: Line 508:
 </code> </code>
   - You will need to enable the Administration pages if you want access to them. Do so by editing your Greenstone installation's ''etc/main.cfg'' file. Change the ''status'' field value from ''disabled'' to ''enabled''. In that case, you may also want to change the admin password for the Adminstration pages. Use a DOS prompt to run: ''gsicontrol.bat configure-admin'' which will allow you to (re)set the password for username ''admin'' (the default admin password is the same as the username).   - You will need to enable the Administration pages if you want access to them. Do so by editing your Greenstone installation's ''etc/main.cfg'' file. Change the ''status'' field value from ''disabled'' to ''enabled''. In that case, you may also want to change the admin password for the Adminstration pages. Use a DOS prompt to run: ''gsicontrol.bat configure-admin'' which will allow you to (re)set the password for username ''admin'' (the default admin password is the same as the username).
-</TAB> +</tabbox>
-</TABAREA>+
  
  
  
-For more detailed instructions on installation, please refer to the [[en:developer:linux_source_install|Linux]]+For more detailed instructions on installation, please refer to the [[en:developer:linux_source_install_gs3|Linux GS3]], [[en:developer:linux_source_install_gs2|Linux GS2]]
 and [[en:developer:mac_source_install|Mac OS]] source installation pages. and [[en:developer:mac_source_install|Mac OS]] source installation pages.
  
Line 566: Line 626:
   - To get the local library server (server.exe) to work from the new location: if your top-level Greenstone installation folder contains the files llssite.cfg and glisite.cfg, delete these. (Note that you should not delete the template files llssite.cfg.in and glisite.cfg.in!) If running the local library server has any issues with Internet Explorer, go to the local library's File>Settings menu and change the Other Browser setting to use Firefox.   - To get the local library server (server.exe) to work from the new location: if your top-level Greenstone installation folder contains the files llssite.cfg and glisite.cfg, delete these. (Note that you should not delete the template files llssite.cfg.in and glisite.cfg.in!) If running the local library server has any issues with Internet Explorer, go to the local library's File>Settings menu and change the Other Browser setting to use Firefox.
   - To get the Apache web server included with Greenstone to work: delete the file lib\java\log4j.properties. (Doing so will ensure that if you execute the gs2-server.bat file--which launches the Greenstone Server Interface--this properties file will be regenerated with the correct value for gsdlhome.)   - To get the Apache web server included with Greenstone to work: delete the file lib\java\log4j.properties. (Doing so will ensure that if you execute the gs2-server.bat file--which launches the Greenstone Server Interface--this properties file will be regenerated with the correct value for gsdlhome.)
- 
  
en/user_advanced/installation.1559120577.txt.gz · Last modified: 2019/05/29 09:02 by anupama