If you have
problems using the given instructions, please subscribe and ask in the developer mailinglist.
Note:
This section is currently being updated for SOPE 4.3 and OGo 1.0a which
change the build and install procedure. Some information might be incorrect,
please provide
feedback
in case you find incorrect information!
Starting with OGo 1.0alpha, OGo has only a single build dependency,
the SOPE application server.
Of course for deployment you might need additional services, like a working
PostgreSQL or Cyrus server.
- Basic ThirdParty Packages
(make, objc, libFoundation, libical)
- SOPE
- Groupware (Logic, DocumentAPI, WebUI)
Note: We try to collect some common build errors in the
Common Build Errors document.
To get a quick overview over the OpenGroupware.org source tree, have a look
at the following picture, which shows the structure of the OpenGroupware.org
repository:
| |
Logic |
main logic part (command objects) |
| |
Database |
database schemata (PostgreSQL, FrontBase) |
| |
DocumentAPI |
logic parts (documents) |
| |
WebUI |
the OGo web interface |
| |
|
AdminUI |
| |
|
Common |
| |
|
Contact |
| |
|
Mailer |
| |
|
NewsUI |
| |
|
OGoForms |
| |
|
OGoFoundation |
| |
|
OpenGroupware.org |
| |
|
PreferencesUI |
| |
|
Project |
| |
|
Resources |
| |
|
Scheduler |
| |
Themes |
image resources for the WebUI |
| |
Tools |
misc. tools |
| |
XmlRpcAPI |
XML-RPC interface to the application |
| |
|
Daemon |
| |
|
Documentation |
| |
PDA |
PDA logic and WebUI |
| |
ZideStore |
native client integration daemon |
| |
|
ZSBackend |
| |
|
ZSFrontend |
| |
|
SoProducts |
| |
|
Protocols |
