[Vala] Migrating to GLib.DBus caused problems

2010-10-11 Thread Gavrilov Maksim 

Hello, guys!

I became tired of warnings when using old dbus-glib method, so I went to 
http://live.gnome.org/Vala/DBusClientSample and tried to compile first 
BlueZ sample exactly as it is written there, but I get a GREAT amount of 
c-mistakes :(


What should I do? Searched all over the Internet, but didn't find any 
answer :(



**
ull...@ulltor-laptop ~/vala-dbus $ valac --pkg gio-2.0 dbus-bluez.vala
/home/ulltor/vala-dbus/dbus-bluez.vala.c:22: error: expected ‘=’, ‘,’, 
‘;’, ‘asm’ or ‘__attribute__’ before ‘BluezProxy’
/home/ulltor/vala-dbus/dbus-bluez.vala.c:23: error: expected ‘=’, ‘,’, 
‘;’, ‘asm’ or ‘__attribute__’ before ‘BluezProxyClass’
/home/ulltor/vala-dbus/dbus-bluez.vala.c:39: error: expected declaration 
specifiers or ‘...’ before ‘GDBusConnection’
/home/ulltor/vala-dbus/dbus-bluez.vala.c:42: error: expected ‘)’ before 
‘*’ token
/home/ulltor/vala-dbus/dbus-bluez.vala.c:49: error: expected ‘)’ before 
‘*’ token
/home/ulltor/vala-dbus/dbus-bluez.vala.c:50: error: expected declaration 
specifiers or ‘...’ before ‘GDBusMethodInvocation’
/home/ulltor/vala-dbus/dbus-bluez.vala.c:51: error: expected ‘)’ before 
‘*’ token
/home/ulltor/vala-dbus/dbus-bluez.vala.c:52: error: expected ‘)’ before 
‘*’ token
/home/ulltor/vala-dbus/dbus-bluez.vala.c:68: error: expected ‘=’, ‘,’, 
‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
/home/ulltor/vala-dbus/dbus-bluez.vala.c:69: error: expected ‘=’, ‘,’, 
‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
/home/ulltor/vala-dbus/dbus-bluez.vala.c:70: error: expected ‘=’, ‘,’, 
‘;’, ‘asm’ or ‘__attribute__’ before 
‘_bluez_dbus_method_info_discover_devices’
/home/ulltor/vala-dbus/dbus-bluez.vala.c:71: error: expected ‘=’, ‘,’, 
‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
/home/ulltor/vala-dbus/dbus-bluez.vala.c:72: error: expected ‘=’, ‘,’, 
‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
/home/ulltor/vala-dbus/dbus-bluez.vala.c:73: error: expected ‘=’, ‘,’, 
‘;’, ‘asm’ or ‘__attribute__’ before 
‘_bluez_dbus_signal_info_discovery_started’
/home/ulltor/vala-dbus/dbus-bluez.vala.c:74: error: expected ‘=’, ‘,’, 
‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
/home/ulltor/vala-dbus/dbus-bluez.vala.c:75: error: expected ‘=’, ‘,’, 
‘;’, ‘asm’ or ‘__attribute__’ before 
‘_bluez_dbus_signal_info_discovery_completed’
/home/ulltor/vala-dbus/dbus-bluez.vala.c:76: error: expected ‘=’, ‘,’, 
‘;’, ‘asm’ or ‘__attribute__’ before 
‘_bluez_dbus_arg_info_remote_device_found_address’
/home/ulltor/vala-dbus/dbus-bluez.vala.c:77: error: expected ‘=’, ‘,’, 
‘;’, ‘asm’ or ‘__attribute__’ before 
‘_bluez_dbus_arg_info_remote_device_found_klass’
/home/ulltor/vala-dbus/dbus-bluez.vala.c:78: error: expected ‘=’, ‘,’, 
‘;’, ‘asm’ or ‘__attribute__’ before 
‘_bluez_dbus_arg_info_remote_device_found_rssi’
/home/ulltor/vala-dbus/dbus-bluez.vala.c:79: error: expected ‘=’, ‘,’, 
‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
/home/ulltor/vala-dbus/dbus-bluez.vala.c:80: error: expected ‘=’, ‘,’, 
‘;’, ‘asm’ or ‘__attribute__’ before 
‘_bluez_dbus_signal_info_remote_device_found’
/home/ulltor/vala-dbus/dbus-bluez.vala.c:81: error: expected ‘=’, ‘,’, 
‘;’, ‘asm’ or ‘__attribute__’ before 
‘_bluez_dbus_arg_info_remote_name_updated_address’
/home/ulltor/vala-dbus/dbus-bluez.vala.c:82: error: expected ‘=’, ‘,’, 
‘;’, ‘asm’ or ‘__attribute__’ before 
‘_bluez_dbus_arg_info_remote_name_updated_name’
/home/ulltor/vala-dbus/dbus-bluez.vala.c:83: error: expected ‘=’, ‘,’, 
‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
/home/ulltor/vala-dbus/dbus-bluez.vala.c:84: error: expected ‘=’, ‘,’, 
‘;’, ‘asm’ or ‘__attribute__’ before 
‘_bluez_dbus_signal_info_remote_name_updated’
/home/ulltor/vala-dbus/dbus-bluez.vala.c:85: error: expected ‘=’, ‘,’, 
‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
/home/ulltor/vala-dbus/dbus-bluez.vala.c:86: error: expected ‘=’, ‘,’, 
‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
/home/ulltor/vala-dbus/dbus-bluez.vala.c:87: error: expected ‘=’, ‘,’, 
‘;’, ‘asm’ or ‘__attribute__’ before ‘_bluez_dbus_interface_info’
/home/ulltor/vala-dbus/dbus-bluez.vala.c:88: error: expected ‘=’, ‘,’, 
‘;’, ‘asm’ or ‘__attribute__’ before ‘_bluez_dbus_interface_vtable’
/home/ulltor/vala-dbus/dbus-bluez.vala.c:123: error: expected ‘)’ before 
‘*’ token
/home/ulltor/vala-dbus/dbus-bluez.vala.c:123: error: expected ‘)’ before 
‘*’ token
/home/ulltor/vala-dbus/dbus-bluez.vala.c: In function 
‘bluez_proxy_class_intern_init’:
/home/ulltor/vala-dbus/dbus-bluez.vala.c:123: error: ‘BluezProxyClass’ 
undeclared (first use in this function)
/home/ulltor/vala-dbus/dbus-bluez.vala.c:123: error: (Each undeclared 
identifier is reported only once
/home/ulltor/vala-dbus/dbus-bluez.vala.c:123: error: for each function 
it appears in.)
/home/ulltor/vala-dbus/dbus-bluez.vala.c:123: error: expected expression 
before ‘)’ token
/home/ulltor/vala-dbus/dbus-bluez.vala.c: In function 
‘bluez_proxy_get_type’:

Re: [Vala] Migrating to GLib.DBus caused problems

2010-10-11 Thread Jürg Billeter 
On Tue, 2010-10-12 at 00:22 +0400, Gavrilov Maksim wrote:
 Hello, guys!
 
 I became tired of warnings when using old dbus-glib method, so I went to 
 http://live.gnome.org/Vala/DBusClientSample and tried to compile first 
 BlueZ sample exactly as it is written there, but I get a GREAT amount of 
 c-mistakes :(
 
 What should I do? Searched all over the Internet, but didn't find any 
 answer :(

What valac version are you using? It should work fine with both, the
current stable release 0.10.0 and the current development release
0.11.0.

Jürg

___
vala-list mailing list
vala-list@gnome.org
http://mail.gnome.org/mailman/listinfo/vala-list

Re: [Vala] Migrating to GLib.DBus caused problems

2010-10-11 Thread Abderrahim Kitouni 
Hi,
 في ث، 12-10-2010 عند 00:22 +0400 ، كتب Gavrilov Maksim:
 Hello, guys!
 
 I became tired of warnings when using old dbus-glib method, so I went to 
 http://live.gnome.org/Vala/DBusClientSample and tried to compile first 
 BlueZ sample exactly as it is written there, but I get a GREAT amount of 
 c-mistakes :(
 
 What should I do? Searched all over the Internet, but didn't find any 
 answer :(
Are you sure you have glib 2.26 (and that vala is using it)? this may
seem obvious, but it's the only thing I can think of.

pkg-config --modversion gio-2.0

should give you the version that is used.

HTH,
Abderrahim

___
vala-list mailing list
vala-list@gnome.org
http://mail.gnome.org/mailman/listinfo/vala-list