This document is outdated, for OGo 1.0a builds, use the OGo 1.0 build guide.
After successfully building SOPE, you can go on with the actual OGo groupware sources, Logic, DocumentAPI and WebUI.
As always, please ensure that your GNUstep environment is loaded prior trying to compile anything. A quick check on this is typing echo $GNUSTEP_USER_ROOT, it should point to something like /home/donald/OGo and not be empty.
Logic => Database => DocumentAPI => WebUI
Buildtime: 3:15 (P4 Mobile 1.8GHz)
cd Logic make -s debug=yes install cd .. Defaults write NSGlobalDomain NGBundlePath \ "$GNUSTEP_USER_ROOT/Library/OpenGroupware.org"
The "Defaults write" is necessary so that the bundle manager can properly locate the various components of OGo (components are implemented as something called a bundle - which is a directory containing resources like images and some executable code).
Check for success:
Buildtime: 0:20 (P4 Mobile 1.8GHz)
cd Database/OGoModel make -s debug=yes install cd ..
Check for success:
Buildtime: 1:27 (P4 Mobile 1.8GHz)
cd DocumentAPI make -s debug=yes install cd ..
Check for success:
Buildtime: 6:47 (P4 Mobile 1.8GHz)
cd WebUI make -s debug=yes install cd Resources make install cd ../.. cd Themes/WebServerResources make install cd ..
This install all the OGo web applications, it installs the language resources packages and it installs the image resources which are located in a different top-level directory (Themes).
Check for success: You should get a WebUI/OpenGroupware.org/OpenGroupware.woa directory. This directory contains the main application bundle, including executable file. You should be able to start the app using:
$ cd WebUI/OpenGroupware.org $ OpenGroupware.woa/ix86/linux-gnu/gnu-fd-nil/OpenGroupware \ -WOPort '"*:20000"'
After compiling the necessary modules, you should follow the install instructions to get a running system. You should definitely access OGo through Apache/mod_ngobjweb instead of working on the SOPE application server directly.