Menu
▾
▴
Re: [Opensync-users] SyncML over bluetooth/obex again
|
From: <nhd...@gm...> - 2006-01-30 17:27:49
|
Hi
I'm trying to build the libyscml-threaded version, I instaled the
libsoup-2.2.9, and patched the libwbxml with the patch in the
libyscml-threaded dir, I have also instaled the openobex-dev package, but
when I run the configure script:
./configure --prefix=3D/home/local/workspace/syncml-testdir
--with-wbxml=3D/home/local/workspace/syncml-testdir
I got:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Unit Tests: Enabled
Tracing: Enabled
Tools: Enabled
Libwbxml: Enabled
The transports are:
Http Client: Enabled
Http Server: Enabled
Obex Client: Disabled
Obex Server: Disabled
Done configuring.
Please review the settings above
If they are ok, build libsyncml and install it.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
I noticide that there is no openobex.pc file in /usr/lib/pkgconfig/ the=
n
I create one:
# Package Information for pkg-config
prefix=3D/usr
exec_prefix=3D${prefix}
libdir=3D${exec_prefix}/lib
includedir=3D${prefix}/include
Name: openobex
Description: openobex adricionado por mim
Version:1.0
Libs: -L${libdir} -lopenobex
Cflags: -I${includedir}
but the configure script don't work, in the configure.ac file I noticed
that the required version is the 1.1,
PKG_CHECK_MODULES(LIBOPENOBEX, openobex >=3D 1.1, HAVE_OPENOBEX=3Dyes,
HAVE_OPENOBEX=3Dno)
Someone can help me?
Regards,
=C1drian L=EDvio
Universidade Federal de Campina Grande - UFCG - www.ufcg.edu.br
Centro de Engenharia El=E9trica e Informatica - CEEI
Unidade Acad=EAmica de Engenharia El=E9trica - UAEE - www.ee.ufcg.edu.br
Laborat=F3rio de Sistemas Embarcados e Computa=E7=E3o Pervasiva -
www.embeddedacademy.org
2006/1/28, Martin Schulze <mar...@hi...>:
>
> I've had a look at the libsyncml-threaded version this evening. From the
> sparse information that I could get, this seems to be the actively
> maintained branch. Attached are patches to this branch and the
> sycml-plugin from trunk.
>
> With these patches applied to current svn, sycml-plugin compiles and
> runs with the libyscml-threaded version. There is no ChangeLog, so I
> have enclosed a short description of the changes below.
>
> msynctool still doesn't work with my mobile phone. It doesn't seem to
> react on the SAN. I gather so much that SAN requires syncml 1.2 (at
> least the way it is currently implemented in libsyncml) and the SGH-D600
> only support syncml 1.1.
>
> Regards,
>
> Martin
>
> _____________________________________________
>
> libsyncml-2006_01_29.diff:
>
> libsyncml/sml_queue.c: Rename the callback functions. Before, the
> callback functions from libopensync/osengine/osengine_queue.c were
> called on my testing platform (leading to SEGFAULT).
> libsyncml/sml_transport.c: Fix typo in the documentation.
> libsyncml/sml_manager.c: Enhance _smlManagerDataHandler() to
> handle to
> only event type SML_TRANSPORT_EVENT_DATA. TODO: Probably, events of type
> SML_TRANSPORT_EVENT_CONNECT_DONE should also be forwarded to
> manager->eventCallback(). However, there is no SML_MANAGER* macro for
> this, yet.
> smlManagerSessionRemove() now calls manager->eventCallback() with
> SML_MANAGER_SESSION_END.
> smlManagerNew(): Fix typo.
> libsyncml/sml_support.c: The idle callback doesn't get called whe=
n
> a
> new thread is started. Work around: _start_main_loop().
>
> syncml-plugin-2006_01_29.diff:
>
> src/syncml_plugin.[hc]: Make it work with the libsyncml-threaded
> branch
> of libsyncml. Use smlManager to manage sessions. I'm not sure whether
> SmlDsSession is used correctly in batch_commit().
> src/syncml-obex-client: Rename 'path' to 'url'. Add new parameter
> 'port'.
>
>
> Am Samstag, den 28.01.2006, 02:18 +0100 schrieb Martin Schulze:
> > Am Samstag, den 28.01.2006, 01:36 +0100 schrieb Martin Schulze:
> > > Am Freitag, den 27.01.2006, 12:43 -0200 schrieb =C1drian L=EDvio:
> > > > Hi
> > > > I am also studing the libsyncml.
> > > >
> > > > Which version of the libsyncml are you studing, the libsyncml
> > > > (trunk) or libsyncml-threaded (branch)?
> > >
> > > I have checked out the trunk version (following the instructions in
> the
> > > wiki). I will try the libsyncml-threaded version ...
> > >
> > > > Do you have any problem building the lib?
> > >
> > > trunk compiles out-of-the-box.
> >
> > So does libsyncml-threaded (with current cvs versions of openobex and
> > libsoup). However, sycml-plugin doesn't compile with
> > libsyncml-threaded ...
> >
> > Regards,
> >
> > Martin
> >
> > > > Thanks.
> > > >
> > > > --
> > > > =C1drian L=EDvio
> > > > Universidade Federal de Campina Grande - UFCG - www.ufcg.edu.br
> > > > Centro de Engenharia El=E9trica e Informatica - CEEI
> > > > Unidade Acad=EAmica de Engenharia El=E9trica - UAEE - www.ee.ufcg.e=
du.br
> > > > Laborat=F3rio de Sistemas Embarcados e Computa=E7=E3o Pervasiva -
> > > > www.embeddedacademy.org
> > > >
> > > >
> > > > 2006/1/26, Martin Schulze <mar...@hi...>:
> > > > I have the impression that the SGH-D600 doesn't support the
> > > > full syncml
> > > > specification. In particular,
> > > > http://www.traud.de/gsm/samsung.htm names
> > > > some restictions on the sync alert sent by the server.
> > > > Therefore, I'm
> > > > trying to gain a more detailed understanding of the
> libsyncml
> > > > code.
> > > >
> > > > Currently, I don't understand the following point:
> > > >
> > > > libopensync obviously waits for a feedback on the
> > > > notification request
> > > > (which my mobile phone doesn't give; see last email). As fa=
r
>
> > > > as I can
> > > > gather from the code, the execution flow should be like
> this:
> > > >
> > > > smlTransportReceive() -> smlSessionReceive() ->
> > > > smlSessionDispatchCommand() -> [chain of callbacks] ->
> > > > osync_context_report_success()
> > > >
> > > > If osync_context_report_success() is not called within 60s
> > > > after the
> > > > notification request, a timeout error is reported (which is
> > > > what I get).
> > > >
> > > > However, even if the SGH-D600 _would_ send an answer, I
> don't
> > > > understand
> > > > how the above call chain can be triggered:
> > > > smlTransportReceive() doesn't
> > > > get called from the OBEX transport layer, neither gets
> > > > smlDsServerRegister() which registers the first callback in
> > > > [chain of
> > > > callbacks]. (Both functions get called from the http
> transport
> > > > layer.)
> > > > Is the OBEX transport layer incomplete? Did I miss
> something?
> > > >
> > > > Regards,
> > > >
> > > > Martin
> > > >
> > > >
> > > > Am Donnerstag, den 26.01.2006, 00:45 +0100 schrieb Martin
> > > > Schulze:
> > > > > $ msynctool --sync testsync --wait
> > > > > ^^^^^^
> > > > >
> > > > > As it turns out, this was _not_ the way to go for the
> > > > SGH-D600.
> > > > >
> > > > >
> > > > > Instead, I had to insert a hack in
> > > > >
> > > > > libsyncml/libsyncml/transport/obex_client.c
> > > > >
> > > > > that sends an AT command
> > > > >
> > > > > AT+CPROT=3D0
> > > > >
> > > > > to the pseudo serial device and listens for the answer
> > > > >
> > > > > CONNECT
> > > > >
> > > > > _before_ sending the OBEX connect request. Then, the
> > > > SGH-D600 answers
> > > > > with a connect response with connection ID 2. Am OBEX put
> > > > (final)
> > > > > request follows and gets a success respone.
> > > > >
> > > > > Unfortunately, nothing more happens. After while,
> msynctool
> > > > quits with
> > > > > the message
> > > > >
> > > > > Member 2 of type syncml-obex-client had an error while
> > > > connecting:
> > > > > Timeout while waiting for a reply to message "CONNECT"
> > > > > ...
> > > > >
> > > > > What exactly it is msynctool waiting for? Any ideas why i=
t
>
> > > > doesn't get
> > > > > what it awaits?
> > > > >
> > > > >
> > > > > Regards,
> > > > >
> > > > > Martin
> > > > >
> > > > >
> > > > > Am Montag, den 23.01.2006, 17:47 +0100 schrieb Martin
> > > > Schulze:
> > > > > > $ msynctool --sync testsync --wait
> > > > > >
> > > > > > This doesn't seem to work for the Samsung - at least I
> > > > have no idea how
> > > > > > to initiate the sync from the SGH-D600, then, so the
> > > > msynctool waits ad
> > > > > > infinitum.
> > > > > >
> > > > > > What changes are needed in libsyncml to trigger the
> > > > syncronization from
> > > > > > the pc side?
> > > > > >
> > > > > > Regards,
> > > > > >
> > > > > > Martin
> > > > > >
> > > > > >
> > > > > > Am Montag, den 23.01.2006, 11:25 +0000 schrieb kevin
> > > > james:
> > > > > > > I've been trying to sync my Nokia 6680 with opensync,
> > > > first trying the
> > > > > > > syncml-http-server, until I realised that it is only
> > > > inbound and my
> > > > > > > laptop doesn't have a "real" IP address.
> > > > > > >
> > > > > > > Then I tried using the obex-client - some info on the
> > > > mailing list
> > > > > > > archive (from around November time) says it's still
> not
> > > > working, don't
> > > > > > > know if that's changed yet. Also I couldn't find any
> > > > info on what the
> > > > > > > config needs to be.
> > > > > > >
> > > > > > > One thing (I think) I did find out is that the
> > > > obex-client is also
> > > > > > > inbound only, so you will need to test it with:
> > > > > > >
> > > > > > > $ msynctool --sync testsync --wait
> > > > > > >
> > > > > > > so that it will wait for a connection.
> > > > > > >
> > > > > > > I am still having problems at the phone end trying to
> > > > use bluetooth/obex
> > > > > > > so I have no messages from opensync saying if anythin=
g
> > > > has worked or
> > > > > > > not. I saw someone mention that some of the devs have
> > > > 6680's - do any of
> > > > > > > them have any advice?
> > > > > > >
> > > > > > > Cheers,
> > > > > > > KEv.
> > > > > > >
> > > > > > >
> > > > > > > On Mon, 2006-01-23 at 01:11 +0100, Martin Schulze
> wrote:
> > > > > > > > Hi!
> > > > > > > >
> > > > > > > > Encouraged by
> > > > > > > >
> > > > > > > >
> > > > http://sourceforge.net/mailarchive/forum.php?thread_id=3D94=
28612&forum_id=3D44467
>
> > > > > > > >
> > > > > > > > I've configured a synchronizing group between my
> > > > evolution environment
> > > > > > > > (plugin evo2-sync) and /dev/rfcomm0 (plugin
> > > > syncml-obex-client) which is
> > > > > > > > bound to the serial port bluetooth service of my
> > > > mobile phone (Samsung
> > > > > > > > SGH-D600). libsyncml and syncml-plugin are fresh
> > > > checkouts from svn. The
> > > > > > > > configuration for the syncml-plugin reads:
> > > > > > > >
> > > > > > > > <config>
> > > > > > > > <username></username>
> > > > > > > > <password></password>
> > > > > > > > <path>/dev/rfcomm0</path>
> > > > > > > > <type>1</type>
> > > > > > > > <usestringtable>2</usestringtable>
> > > > > > > > <onlyreplace>0</onlyreplace>
> > > > > > > > <contact_db>addressbook</contact_db>
> > > > > > > > <calendar_db>calendar</calendar_db>
> > > > > > > > <task_db>tasks</task_db>
> > > > > > > > </config>
> > > > > > > >
> > > > > > > > However, I run into the same troubles discussed in
> > > > > > > >
> > > > > > > >
> > > >
> http://sourceforge.net/mailarchive/forum.php?thread_id=3D8902424&forum_id=
=3D44467
> > > > > > > >
> > > > > > > > E.i.
> > > > > > > >
> > > > > > > > $ msynctool --sync testsync
> > > > > > > >
> > > > > > > > yields:
> > > > > > > >
> > > > > > > > Synchronizing group "testsync"
> > > > > > > > Member 1 of type evo2-sync just connected
> > > > > > > > Member 2 of type syncml-obex-client had an error
> while
> > > > connecting: No
> > > > > > > > success
> > > > > > > > Member 1 of type evo2-sync just disconnected
> > > > > > > > All clients have disconnected
> > > > > > > > The sync failed: Unable to connect one of the
> members
> > > > > > > > Error synchronizing: Unable to connect one of the
> > > > members
> > > > > > > >
> > > > > > > > The trace output from the syncml-obex-client plugin
> > > > reads as follows:
> > > > > > > >
> > > > > > > > [1137969737.641293] +++++++++ This is the clien=
t
> > > > #2
> > > > > > > > (syncml-obex-client plugin) of group testsync
> > > > +++++++++
> > > > > > > > [1137969737.746230 ]
> > > > >>>>>>> client_message_handler(0x80638f0,
> > > > > > > > 0x8077aa0, 0x80614e0)
> > > > > > > > [1137969737.746285] [CLI] DEBUG: Client
> > > > message handler
> > > > > > > > called for message "CONNECT"
> > > > > > > > [1137969737.746306]
> > > > >>>>>>> osync_member_connect(0x80625c0,
> > > > > > > > 0xb7ebbd70, 0x8077aa0)
> > > > > > > > [1137969737.746330] >>>>>>>
> > > > > > > > client_connect(0x8077e08)
> > > > > > > > [1137969741.853995]
> > > > >>>>>>>
> > > > > > > > osync_context_report_osyncerror(0x8077e08,
> > > > 0xb6b99244:(No success))
> > > > > > > > [1137969741.854070]
> > > > [CLI] WARNING:
> > > > > > > > Member is replying with message 0x807ef48 to messag=
e
> > > > 0x8077aa0:"CONNECT"
> > > > > > > > with error 1: No success
> > > > > > > > [ 1137969741.854106]
> > > > <<<<<<<
> > > > > > > > osync_context_report_osyncerror
> > > > > > > > [1137969741.854126] <--- ERROR
> ---
> > > > client_connect:
> > > > > > > > No success
> > > > > > > > [1137969741.854145]
> > > > <<<<<<< osync_member_connect
> > > > > > > > [1137969741.854163]
> > > > <<<<<<< client_message_handler
> > > > > > > >
> > > > > > > > Does anybody have an idea where the problem lies? T=
o
> > > > start with: is it
> > > > > > > > more likely from the OBEX transport layer or a
> SyncML
> > > > related problem?
> > > > > > > > Is there anything I can do to help getting the thin=
g
> > > > to work?
> > > > > > > >
> > > > > > > > The only information related to SyncML with my
> mobile
> > > > phone I've found
> > > > > > > > up to now is here:
> > > > > > > >
> > > > > > > > http://www.traud.de/gsm/samsung.htm
> > > > > > > >
> > > > > > > > I have just e-mailed Samsung about the SyncML
> version
> > > > that the SGH-D600
> > > > > > > > is using. Has it already been clarified, how to fin=
d
> > > > the correct values
> > > > > > > > of the XXX_db parameters in the configuration of th=
e
> > > > syncml-plugin?
> > > > > > > >
> > > > > > > > Regards,
> > > > > > > >
> > > > > > > > Martin
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > -------------------------------------------------------
> > > > > > > > This SF.net email is sponsored by: Splunk Inc. Do
> you
> > > > grep through log files
> > > > > > > > for problems? Stop! Download the new AJAX search
> > > > engine that makes
> > > > > > > > searching your log files as easy as surfing
> > > > the web. DOWNLOAD SPLUNK!
> > > > > > > >
> > > >
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486&dat=
=3D121642
> > > > > > > > _______________________________________________
> > > > > > > > Opensync-users mailing list
> > > > > > > > Ope...@li...
> > > > > > > >
> > > > https://lists.sourceforge.net/lists/listinfo/opensync-users
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > -------------------------------------------------------
> > > > > > This SF.net email is sponsored by: Splunk Inc. Do you
> grep
> > > > through log files
> > > > > > for problems? Stop! Download the new AJAX search
> engine
> > > > that makes
> > > > > > searching your log files as easy as surfing
> > > > the web. DOWNLOAD SPLUNK!
> > > > > >
> > > >
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486&dat=
=3D121642
> > > > > > _______________________________________________
> > > > > > Opensync-users mailing list
> > > > > > Ope...@li...
> > > > > >
> > > > https://lists.sourceforge.net/lists/listinfo/opensync-users
> > > > >
> > > > >
> > > > >
> > > > > -------------------------------------------------------
> > > > > This SF.net email is sponsored by: Splunk Inc. Do you gre=
p
> > > > through log files
> > > > > for problems? Stop! Download the new AJAX search engine
> > > > that makes
> > > > > searching your log files as easy as surfing
> > > > the web. DOWNLOAD SPLUNK!
> > > > >
> > > >
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486&dat=
=3D121642
> > > > > _______________________________________________
> > > > > Opensync-users mailing list
> > > > > Ope...@li...
> > > > >
> https://lists.sourceforge.net/lists/listinfo/opensync-users
> > > >
> > > >
> > > >
> > > > -------------------------------------------------------
> > > > This SF.net email is sponsored by: Splunk Inc. Do you grep
> > > > through log files
> > > > for problems? Stop! Download the new AJAX search engine
> that
> > > > makes
> > > > searching your log files as easy as surfing
> > > > the web. DOWNLOAD SPLUNK!
> > > >
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486&dat=
=3D121642
> > > > _______________________________________________
> > > > Opensync-users mailing list
> > > > Ope...@li...
> > > > https://lists.sourceforge.net/lists/listinfo/opensync-users
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > > -------------------------------------------------------
> > > This SF.net email is sponsored by: Splunk Inc. Do you grep through lo=
g
> files
> > > for problems? Stop! Download the new AJAX search engine that makes
> > > searching your log files as easy as surfing the web. DOWNLOAD
> SPLUNK!
> > > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=103432&bid#0486&dat=121=
642<http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid%103432&bid#0486&dat%12164=
2>
> > > _______________________________________________
> > > Opensync-users mailing list
> > > Ope...@li...
> > > https://lists.sourceforge.net/lists/listinfo/opensync-users
> >
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc. Do you grep through log
> files
> > for problems? Stop! Download the new AJAX search engine that makes
> > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=103432&bid#0486&dat=12164=
2<http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid%103432&bid#0486&dat%121642>
> > _______________________________________________
> > Opensync-users mailing list
> > Ope...@li...
> > https://lists.sourceforge.net/lists/listinfo/opensync-users
>
>
>
|
