Skip to content

OGo Docs

Sections
Personal tools
You are here: Home » Members » whitemice's Home » Misc. Stuff. » Building OpenGroupware

Building OpenGroupware

Document Actions
How to build OpenGroupware trunk the easy way.
There are build instructions for building the entire OpenGroupware infrastructure here. But there is an easy (cheaters) way if all you want to do is hack on OpenGroupware and you aren't interested in all that other stuff: libfoundation, SOPE, etc...

NOTE: Instructions for building OpenGroupware packages can be found here.
  1. Install OpenGroupware from packages, include ALL the packages.
  2. Setup OpenGroupware so it is WORKING, at least as much as possible.
    • On any reasonably mainstream distribution this is pretty trivial these days; if you are using some crazy niche distribution then switch to OpenSuSE. :)
  3. Check out the code from SVN.
    1. svn co http://svn.opengroupware.org/SOPE/branches/sope-4.6
      • OpenGroupware 1.1.x is intended to be built with SOPE 4.6
    2. mv sope-4.6 sope
    3. svn co http://svn.opengroupware.org/OpenGroupware.org/trunk
    4. mv trunk opengroupware.org
  4. Now you can commence with building...
    1. export GNUSTEP_MAKEFILES=/usr/local/OGo-GNUstep/Makefiles
    2. cd sope
    3. ./configure --prefix=/usr/local
    4. make
      • You may want to do a make install at this point; depends on what you are trying to accomplish. If native packages aren't available for your distribution + version building your own copy of SOPE can work around several bugs introduced by ABI incompatibility.
      • The SOPE code includes ngobjweb and libFoundation.
    5. cd ..
    6. cd opengroupware.org
    7. ./configure --without-pisock --enable-debug
      • Current distributions ship with a later version of pilot-link, so without --without-pisock the build may fail. Even if the PDA code compiles it doesn't work with Palm OS 5 devices.
    8. make


And sometime later you will have compiled OpenGroupware libraries and binaries!

Now you can hack and compile all you want. The binaries are build in "shared_debug_obj" folders, and you can move your custom libraries and executables over the top of the ones installed by your package manager (saving the originals, of course). I usually save the one from the package manager as filename.packaged and my custom ones as filename.custom and make a sym-link from filename to the one I want to run. This way you continue to use the same start/stop scripts, etc....

awilliam@aleph:~/OGo/trunk> file WebUI/Main/shared_debug_obj/ogo-webui-1.1
WebUI/Main/shared_debug_obj/ogo-webui-1.1: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.4, dynamically linked (uses shared libs), for GNU/Linux 2.6.4, not stripped
awilliam@aleph:~/OGo/trunk> file XmlRpcAPI/shared_debug_obj/ogo-xmlrpcd-1.1
XmlRpcAPI/shared_debug_obj/ogo-xmlrpcd-1.1: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.4, dynamically linked (uses shared libs), for GNU/Linux 2.6.4, not stripped
Created by whitemice
Last modified 2007-04-13 05:29 PM
 

Powered by Plone

This site conforms to the following standards: