Make sure to get the latest sources, go to the topdirectory and either type make. Make will inform you of the possible actual make commands. Currently these are a combination of a frontend with a borgcore. There are two possible borgcores. cborg and bborg:

cborg: the borgcore written in C.
bborg: the borgcore written in Borg itself.

The possible user interfaces are:

kborg: a KDE 1 frontend
wborg: a windows frontend
tborg: a text frontend
hborg: a html frontend

Specify which frontend and borgcore you want is done by the two first letter of the make command. For example make kcborg will compile a KDE frontend and link it to a cborgcore. make kbborg will compile a KDE frontend and link it with a bborgcore. And so on.

Of course, it's quite difficult to make source which compiles on different architectures. Teherefore we created a file Defines.h in the toplevel directory which checks your hostname and creates a set of defines. This file can and should be changed to refelect your specific machine. The Defines.h file contains platform specific information, such as where to find libraries, where to look for include files and the location of binaries. In addition this file also contains the current version number.
 

Linux/Kde1

• flex to compile the syntax
• bison to compile the grammar
• kde1.1.2 libraries
• qt1.44 or qt1.45 libraries
• gcc/g++
• readline libraries
• cvs 1.11

KBORG_MOC which should point to the moc (Meta Object compiler) of QT 1.4. This is probably located in /usr/local/qt-1.44/bin/moc, or another directory.
KBORG_INCLUDE_PATH which should contain options to g++ to find the qt and kde includes. Most of the time these can be found in -I/usr/local/qt/include -I/usr/local/kde/include
KBORG_LIBRARY_PATH which should point to the locations of the .a libraries of qt, kde and X11R6. Probably these will be located in -L/usr/local/qt/lib -L/usr/local/kde/lib -L/usr/X11R6/lib
 

Linux/Kde2

• Gcc/g++
• flex to compile the syntax
• bison to compile the grammar
• kde1.1.2 libraries.
• qt1.44 or qt1.45 libraries
• readline libraries
• cvs 1.11

a. Install qt1 & the kde1 libraries (kdelibs) in some directory (NOT the default, I too /usr/local/qt1 & /usr/local/kde1, resp)
b. Make sure /usr/local/kde1/bin is in the path, /usr/local/qt1/lib is included in LD_LIBRARY_PATH
c. Enter the locations of these libraries in Defines.h as specified in the above section.
d. make kcborg

You can find the QT and KDE1 libs on ftp://progpc26.vub.ac.be/cborg/QtKde1Libs/ Normally you will only need qt_1_44.tgz and kdelibs.tgz. Unzip the file in the root of you system. Execute /install/doinst.sh and start ldconfig -v !
 

PalmOS

• gcc >2.95 <3.0
• pilrc
• prctools
• palmos 3.5 headers
• flex to compile the syntax
• bison to compile the grammar
• cvs 1.11

Cross Compilation under Linux

You can find all the tools described here on the palmos website unless said otherwise.

• Stable GCC 2.95 or higher (Should ship with any recent linux distribution)
• The PRC tools for linux. Attention, the tools on the palm site are not working correctly!!! The best thing to do is to find a more recent version than recommended on the palmos website. The 2.1 pre 3 (2.0.92) version works best. You can find it at: http://sourceforge.net/projects/prc-tools
• PilRC tools (nescesary to create forms for you're program): Follow the link on the palmos website. Be sure to download the latest patch version in order to have a troubleless compilation.


Follow these instructions to install the tools:

• Unpackage the file by typing the following command:

$tar -xvpfz pilrc_src.tgz

• Change to the PilRC directory (for example, pilrc-2.5c) and type the following comands:

$./configure

If configure gives an error, you have most likely a GCC version below 2.95

$make

If you encounter any problems here, be sure you have the latest version with the latest patch level
• Become the root and then type the following command:

$make install

This copies a PilRC binary file to the usr/local/bin directory
 
• The palmos SDK files for the PalmOS you like to work with. On the current models the PalmOS 3.5 is most likely to be used this can be found at:http://www.palmos.com/dev/tools/sdk/sdk2452534/sdk35.html. The most recent and new models ship with version 4.0 of the palmOS
• Unpackage the SDK package to obtain the contents.
• You need to add the header files and libraries to your "palmdev" directory.The default is /usr/local/palmdev
• In your "palmdev" directory, create a directory "/sdk-3.5" and create two subdirectories of it:

/include directory
/lib directory

• Copy the contents of "Palm OS 3.5 Support/Incs" to the new /include directory.
• Copy the contens of "Palm OS 3.5 Support/GCC Libraries" to the new /lib directory. Be sure to install the latest SDK patch here too. Just be carefull, if you simply overwrite the existing m68k library with the new one, you will erase a crucial library (who has not been updated) Simply copy the 2 new files into the top directory .../lib/m68k.../ overwriting the 2 existing files and leaving the 3rd unharmed.
• You can now compile your programs using Palm OS 3.5 headers and libraries by adding a "-palmos3.5" option to your compile and link commands. For example:

$ m68k-palmos-gcc -O2 -o hello hello.c -palmos3.5

• To use the Palm OS 3.5 headers and libraries by default, you can change the "sdk" symbolic link in the "palmdev" directory to point to the new SDK by typing the following commands:

$ cd /usr/local/palmdev
$ rm sdk=20
$ln -s sdk-3.5 sdk

• The resulting directory structure should match this structure:

/usr/local/palmdev/sdk-3.5
/usr/local/palmdev/sdk-3.5/include
/usr/local/palmdev/sdk-3.5/include/Core
/usr/local/palmdev/sdk-3.5/include/Core/System
/usr/local/palmdev/sdk-3.5/include/Dynamic
/usr/local/palmdev/sdk-3.5/lib
/usr/local/palmdev/sdk-3.5/lib/m68k-palmos-coff=20

These are all you need to compile for palm/visor
The compilation itself is pretty straightforward and always happens in three steps :

$ m68k-palmos-gcc -O2 -o hello hello.c -palmos*.*
This compiles you're palmos program using the palm library's
$ m68k-palmos-obj-res hello
$ build-prc hello.prc "Hello, World" WRLD *.hello.grc

The latter links you're compiled program with a form (mostly in a grc file). It is easiest to automate these steps using a makefile. Look at the pborg makefile for an example.

When those three operations are succesfull you will find a .prc file. Upload this file to you're palm/visor using coldsync, palmpilot or some other exotic linux tool and hope for the best.

Freebsd

Windows

• cygwin tools at http://www.cygwin.com/
• wincvs

Solaris

Online Source Access

Cvs Repository -- was once online, no longer supported

Source Statistics -- was once online, no longer supported

Borg Crossreferencer -- was once online, no longer supported

Source Conventions

• We do not use // - comments in the cborgcore. This because a number of macinotsh comilers are completely unable to deal with this kind of (valid) comments.
• If you add a comment add your name.
• In the cborgcore we NEVER includes specific headers. A source file can define something like #define NeedFile. The correct headers will be included from AllHeaders.h. AllHeaders.h loads all necessary headers for a certain platform. This is done by including standard C headers and by including platform specific headers (StdLinux.h, StdSolaris.h and so on). In these file you can include whatever you want. As long as it compiles of course.

[Non]-Frequently asked Questions