PDA

View Full Version : Compilation problems!


convulted
04-28-2007, 08:19 AM
Hey all,

I am trying to compile a 15-line C file that uses the OSSO-IC API (my target device is a 770 running OS2006). However, I cannot get it to compile. It keeps giving me errors such as:
/usr/include/osso-ic.h:32:23: dbus/dbus.h: No such file or directory
In file included from /usr/include/osso-ic.h:33,
from c.c:3:
/usr/include/libosso.h:28:18: glib.h: No such file or directory
/usr/include/libosso.h:35:32: dbus/dbus-protocol.h: No such file or directory
In file included from /usr/include/osso-ic.h:33,
from c.c:3:

I tried using pkg-config but I do not really understand what it does, or how to use it, and did not solve the problems.

Can anyone help?
Thanks!

yerga
04-28-2007, 09:30 AM
It seems that you lack the Glib and Dbus development libraries. They would be the packages libglib2.0-dev and libdbus-1-dev or with a similar name.


Cheers.

convulted
04-28-2007, 10:22 AM
Where would I go about getting them? apt-get complains that libglib2.0-dev has been obsoleted...

ArnimS
04-28-2007, 02:06 PM
Your compiler invocation is failing to -I include the header files properly. dbus.h for example is in /usr/include.

pkg-config is a helper tool to add the needed includes and libraries to your gcc invocation. You can look at other sources for examples of pkg-config usage.

I don't think you have a problem with installed packages.

For Maemo_Dev_Platform_v2.2 / IT 2006

> apt-cache policy libglib2.0-dev
libglib2.0-dev:
Installed: 2.8.6-1osso5
Candidate: 2.8.6-1osso5

convulted
04-28-2007, 04:25 PM
Re-downloaded vmWare appliance and started from scratch. The problem is that libglib is not included with the armel rootstrap, but it is with the i386 rootstrap (see the file listings at http://repository.maemo.org/stable/gregale/). I will try a new target using the i386 rootstrap.

*edit*

Didn't work. Oh, and btw, I don't have dbus.h in my /usr/include!

convulted
04-28-2007, 06:44 PM
Fixed the problem by adding the header files manually (copied off the Internet). Now I need to figure out how to make an IAP connection "stick" and not turn itself off in a few seconds...