On Thu, 2010-07-15 at 10:57 +0100, Sascha Peilicke wrote:
On Thursday 15 July 2010 11:51:52 you wrote:
> On Thu, 2010-07-15 at 10:37 +0100, Sascha Peilicke wrote:
> > ObexTransportAgent.cpp:34:29: fatal error: glib/giochannel.h: No such
> > file or directory compilation terminated.
>
> Where is glib/giochannel.h installed? What is the g++ invocation?
/usr/include/glib-2.0/glib/giochannel.h
Funnily enough, if I include only glib.h in ObexTransportAgent.cpp it isn't
found either.
libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../.. -
I/home/saschpe/projects/c_cpp/SyncEvolution/syncevolution/src/build-
synthesis/src -I/usr/include -I/usr/include/KDE -I/usr/include/qt4 -
I../../test -I../../src -
DSYNCEVO_BACKEND=\"/usr/local/lib/syncevolution/backends/\" -
DXML_CONFIG_DIR=\"/usr/local/share/syncevolution/xml\" -
DTEMPLATE_DIR=\"/usr/local/share/syncevolution/templates\" -
DLIBDIR=\"/usr/local/lib\" -
I/home/saschpe/projects/c_cpp/SyncEvolution/syncevolution/src/build-
synthesis/src -g -MT libsyncevolution_la-ObexTransportAgent.lo -MD -MP -MF
.deps/libsyncevolution_la-ObexTransportAgent.Tpo -c ObexTransportAgent.cpp -o
libsyncevolution_la-ObexTransportAgent.o
Are you perhaps:
* not enabling D-Bus (no --enable-dbus-service) and
* disabling EDS (--disable-ecal --disable-ebook)
* and not using the latest sources from master?
There was a bug in configure that it didn't check for glib in this
combination, which is fixed on master. Your configure-pre.in should
contain:
# SoupTransportAgent depends on glib
case "$TRANSPORT" in *libsoup*) need_glib=yes;; esac
Or perhaps you are no longer using libsoup?
I just realize that the OBEX transport does not declare its dependency
on glib either. So underneath the line
AC_DEFINE(ENABLE_OBEX, 1, [define if openobex library is available])
there should be a
need_glib=yes
Does that help?
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.