@@ -1,11 +1,13 @@  !!! Compiling Kexi from Subversion  @@@   +Simple version: you can also [download the source tarball|http://www.kexi-project.org/wiki/wikiview/index.php?Source]. +  !! Introduction    The KDE project uses the [Subversion|http://subversion.tigris.org/] version control system as a repository for source code. Kexi can be found in the KOffice directory of the repository. An 'anonymous mirror' provides public access to source code.   -This page describes how to build Kexi from the KDE's anonymous Subversion repository. You'll need a copy of [Subversion|http://subversion.tigris.org/] (your distribution probably contains needed binaries). The subversion protocol uses port 3690, so, if you have a firewall in place, it's worth checking that it will allow subversion traffic. You can use your own SVN accountm if you have one. In this case, replace svn://anonsvn.kde.org/home/kde/trunk/koffice/ with https://svn.kde.org/home/kde/trunk/koffice/. +This page describes how to build Kexi from the KDE's anonymous Subversion repository. You'll need a copy of [Subversion|http://subversion.tigris.org/] (your distribution probably contains needed binaries). The subversion protocol uses port 3690, so, if you have a firewall in place, it's worth checking that it will allow subversion traffic. You can use your own SVN account, if you have one. In this case, replace svn://anonsvn.kde.org/home/kde/branches/koffice/1.6/koffice/ with https://svn.kde.org/home/kde/branches/koffice/1.6/koffice/.    (not available for now)  ~~If you can't access the subversion server, you might want to try using the daily KOffice snapshot at~~

@@ -21,42 +23,60 @@    If you are using Subversion because you want to help develop Kexi, you might want to read step 5 only of [Working with Existing Applications in KDE CVS| http://kde.ground.cz/tiki-index.php?page=How+To+Use+KDevelop+with+KDE+CVS].   -* Browse Kexi in [trunk|http://websvn.kde.org/trunk/koffice/kexi/] +You can also [browse Kexi source code tree|http://websvn.kde.org/branches/koffice/1.6/koffice/kexi/]. + +!Things to Remember +* Please uninstall any KOffice package if you have such installed independently (these not coming from this particular compilation). Otherwise you'll encounter hard to locate crashes or misbehaviour. +* Do not forget about installing Kexi always after compiling it - without this things will not work properly or will crash. Use 'make install' or 'unsermake install' commands from lib/ and kexi/ source code subdirectories. +* If you compiled Kexi from source code obtained via Subversion, it's good idea to '''keep''' your source code directory for later. Then you can just use 'svn up' commands to '''quickly''' update the source code to the newest version, getting all new features and fixes. Then, compile again using 'make' or 'unsermake' commands, what is usually much faster andeasier than starting from scratch with downloading and recompiling Kexi. +* If you want to use unsermake, sometimes (depending on your OS distribution, e.g. reported for Kubuntu) unsermake is unable to find ''aclocal'' command. The reason can be that in your system aclocal belongs to automake, not autoconf. If this is the case, install automake, even if you do not plan to use it ([more info|http://wiki.kde.org/tiki-index.php?page=ErrorMessages#_autoconf_not_found]).    !! Short version +First, using ''unsermake'' instead of automake is recommended - it is faster and convenient way for performing compilations. Read the documentation how to get and install [unsermake|http://www.kde.me.uk/index.php?page=unsermake] (some distributions offer automake packages). +  The following is a short summary of the process. See subsequent sections for step-by-step instructions: - svn co -N svn://anonsvn.kde.org/home/kde/trunk/koffice/ + ~~svn co -N svn://anonsvn.kde.org/home/kde/trunk/koffice/~~ + svn co -N svn://anonsvn.kde.org/home/kde/branches/koffice/1.6/koffice/   cd koffice   svn co svn://anonsvn.kde.org/home/kde/branches/KDE/3.5/kde-common/admin   svn up kexi   svn up lib + +To skip compilation of certain KOffice apps, type something like: + export DO_NOT_COMPILE="kchart kdgantt kformula koshell krita kugar kword" + +If you're using automake:   make -f Makefile.cvs +Use "unsermake -f Makefile.cvs" instead if you're using [unsermake|http://www.kde.me.uk/index.php?page=unsermake]. You should see "*** Finished" message. Then:   ./configure --enable-debug=full --prefix=`kde-config --prefix`   perl admin/am_edit # shouldn't be necessary - why is it needed sometimes? +  And finally, if you're using automake, type this to build Kexi and install: - make - make install + cd koffice/lib && make && make install + cd ../kexi && make && make install  or, if you're using [unsermake|http://www.kde.me.uk/index.php?page=unsermake]: - unsermake - unsermake install + unsermake && unsermake install  (to install you may need root priviledges)    !! Requirements  ! Disk space -* A subversion of checkout of Kexi is currently about 38MB. -* A complete build requires about 187MB. +* KOffice source code coming from the Subversion repository is currently about 120MB (the same for the tarball version). kexi/ and lib/ subdirectories alone are 20MB large. +* A complete build can require even 400MB.    ! Package requirements  Kexi can be built on KDE 3.2 or newer. -The kdelibs development files are required to build Kexi, plus the development files for building support for database servers. The kdelibs files may be packaged for your distribution as kdelibs-dev or kdelibs-devel. +The kdelibs development files are required to build Kexi, plus the development files for building support for database servers. The kdelibs files may be packaged for your distribution as something like kdelibs-dev or kdelibs-devel.   -See the [Notes|http://www.kexi-project.org/wiki/wikiview/index.php?UsingSubversion#_Notes] section below for lists of packages required for [building on Debian|http://www.kexi-project.org/wiki/wikiview/index.php?UsingSubversion#_Building_Kexi_on_Debian]. +See the [Notes|http://www.kexi-project.org/wiki/wikiview/index.php?UsingSubversion#Notes] section below for lists of packages required for [building on Debian|http://www.kexi-project.org/wiki/wikiview/index.php?UsingSubversion#Building_Kexi_on_Debian].    If you can tell us which packages are needed to build Kexi on your distribution, please email [us|mailto:martin.ellis@kdemail.net]    !! Building  ! Building from 'trunk'  'Trunk' is usually used for the latest development version, and this section explains how to build it. + +__NOTE: trunk is now in transition to KDE4, so could not compile. Please replace every occurence of 'trunk/koffice/' with 'branches/koffice/1.6/koffice/' below.__ +    First, check out a copy from the anonymous subversion server:   svn co -N svn://anonsvn.kde.org/home/kde/trunk/koffice/

@@ -69,6 +89,7 @@    Then build the configure script and Makefiles:   make -f Makefile.cvs +(use "unsermake -f Makefile.cvs" instead if you're using [unsermake|http://www.kde.me.uk/index.php?page=unsermake])    It might be a good idea to have a quick look at which configuration options are available:   ./configure --help

@@ -77,11 +98,11 @@   ./configure --enable-debug=full --prefix=`kde-config --prefix`    And finally, if you're using automake, type this to build Kexi and install: - make - make install + cd koffice/lib; make; make install + cd ../kexi; make; make install  or, if you're using [unsermake|http://www.kde.me.uk/index.php?page=unsermake]: - unsermake - unsermake install + cd koffice/lib && unsermake && unsermake install + cd ../kexi && unsermake && unsermake install  (to install you may need root priviledges)    ! Managing different versions of Kexi

@@ -89,7 +110,7 @@    !! Compiling additional components  !Form Designer -To compile [Form Designer|KFormDesigner] ([FAQ|FormDesignerFAQ]) as a standalone application, compile and install Kexi as above, then: +(obsolete) To compile [Form Designer|KFormDesigner] ([FAQ|FormDesignerFAQ]) as a standalone application, compile and install Kexi as above, then:   cd kexi/formeditor/test/   make   make install

@@ -142,9 +163,9 @@    The following Kexi configure options are available __if__ the configure script cannot find the pq development files:  * use PostgreSQL(libpq)-includes installed in this directory - --with-pgsqlincdir=DIR + --with-pgsql-includes=DIR  * use PostgreSQL(libpq)-libraries installed in this directory - --with-pgsqllibdir=DIR + --with-pgsql-libraries=DIR    '''pqxx library''': We recommend that you use packages for your distribution with the appropriate pqxx development files, but you can also compile from [source|http://gborg.postgresql.org/project/libpqxx/download/download.php].

@@ -158,9 +179,9 @@    The following Kexi configure options are available __if__ the configure script cannot find the pqxx development files:  * specify that PostgreSQL(libpqxx) includes are installed in DIR - --with-pqxxsincdir=DIR + --with-pqxx-includes=DIR  * specify that PostgreSQL(libpqxx) libraries are installed in DIR - --with-pqxxslibdir=DIR + --with-pqxx-libraries=DIR      ! Building Kexi on Debian