[Gpe-list] gpe-expenses releases at SourceForge

[Neil Williams]

On Sat, 30 Dec 2006 14:13:13 +0100
Koen Kooi <koen at dominion.kabel.utwente.nl> wrote:

> > gpe-expenses uses QOF.
>
> It would be nice if gpe-expenses checks which version of QOF is installed during
> configure. I spent a few minutes scratching my head over various errors gcc was throwing
> at me, when I realised that gpe-expenses needs 0.7.2.

It does check but it sounds like the check is not sufficiently robust.

AC_ARG_WITH(qof, [  --with-qof=path          prefix for Query Object
Framework - QOF (auto)])
QOF_REQUIRED=0.7.2

> Anyway, I fixed 0.6.0 in OE and added 0.7.2:
> http://www.openembedded.org/filebrowser/org.openembedded.dev/packages/qof
>

What errors do you get because of this section (removed by patches in
OE):
-INCLUDES = \
-	-I$(includedir)

I can investigate removing these from upstream if I know what happens
with them present.


> > QOF depends on glib-2.0. gpe-expenses uses a sqlite backend via QOF.
>
> I had to disable -Werror due to some warnings about gs_list in qof 0.6.0 and 0.7.2

Can you provide a build log? I use -Werror for all builds on two
different platforms. Debian builds with -Werror for 12 architectures
without problems. Please don't disable it. What version of glib-2.0 are
you using?

As you can see here:
http://buildd.debian.org/fetch.cgi?pkg=qof;ver=0.7.2-1;arch=arm;stamp=1167401886
QOF builds with -Werror enabled on arm without changes.

qof configuration summary:
===========================

CFLAGS      :    -Werror -Wdeclaration-after-statement -Wno-pointer-sign


> After all that, I added gpe-expenses 0.0.6 into OE:
> http://www.openembedded.org/filebrowser/org.openembedded.dev/packages/gpe-expenses

> It's in the feeds for the angstrom distribution as well now:
> http://www.angstrom-distribution.org/repo/?action=details&pnm=gpe-expenses
>
> That shows a few heavy dependencies like popt and libxml2, would it be possible to use the
> standard glib and gtk functions for that?

QOF is not solely for embedded devices, it has a wider role and
supports configure options to make it easier to use on embedded
systems. I've tried to document the build options here:
http://qof.sourceforge.net/hacking.html which is reproduced within the
distributed tarball as the file 'HACKING'. I guess some more content is
needed - what information do you consider missing from the HACKING file?

./configure --help contains:
  --disable-deprecated-qof
                          don't use deprecated QOF functions
  --disable-deprecated-glib
                          don't use deprecated glib functions
  --enable-embedded         Enable the SQLite backend for embedded
systems and DISABLE the QSF XML backend. (no)
  --enable-sqlite           Enable the SQLite backend module
                          alongside the QSF XML backend. (no)
  --enable-doxygen        enable documentation generation with doxygen
(auto)

For embedded systems, I'd recommend --enable-embedded --disable-doxygen
(maybe add --disable-deprecated-glib).

You can build QOF to not use libxml2 -

Basically, what you want is:
1. Build without libgda (as you do)
2. Pass the --enable-embedded option to configure which omits libxml2
and builds the sqlite backend only.

I'll add some more documentation on that. Where's the best place - the
HACKING within QOF, the README within QOF or somewhere within
gpe-expenses (that README probably does need some extending)?


--


Neil Williams
=============
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.linuxtogo.org/pipermail/gpe-list/attachments/20061230/e9c2a5a0/attachment.pgp