Re: [Opensync-users] Opensync 0.36 on Feisty: Stuck with: OBEX Transport not enabled in this build

[Gerd B. <ger...@go...>]

Solved (by accident to be honest).

I typed

cmake .

(wanted to type ccmake as Daniel told me).

This gave another output:

  root@feisty:~/libsyncml/build# cmake .
-- checking for one of the modules 'openobex>=1.1'
--   found openobex, version 1.3
-- checking for one of the modules 'libsoup-2.2>=2.2.91;libsoup2>=2.2.91'
-- checking for one of the modules 'bluez'
--   found bluez, version 3.9
-- checking for one of the modules 'check'
-- Could NOT find CHECK
-- ==================================================
-- building tools                               ON
-- tracing tools                                ON
-- unit tests                                   OFF
-- http transports                              OFF
-- obex transports                              ON
-- obex over bluetooth transports               ON
-- Configuring done
-- Generating done
-- Build files have been written to: /root/libsyncml/build
root@feisty:~/libsyncml/build#

Rebuilding left me with a slightly bigger library, which now no longer 
complains about OBEX Transport not enabled.

Thanks

Gerd

Gerd Bavendiek schrieb:
> Daniel Gollub schrieb:
>> On Freitag 01 Februar 2008, you wrote:
>>> Daniel Gollub schrieb:
>>>> On Freitag 01 Februar 2008, Gerd Bavendiek wrote:
>>>>> ERROR: OBEX Transport not enabled in this build
>>>> Which version of libsyncml?
>>> I did:
>>>
>>> root@feisty:~# svn co http://svn.opensync.org/libsyncml/trunk libsyncml
>>>
>>>> Is libsyncml build with OBEX transport?
>>> How can I check / ensure this ?
>>
>> Run within your build directory:
>> ccmake .
>>
>>
>> Very likely OBEX transport got enabled by default - if openobex 
>> headers (devel package) were installed and found.
>>
> 
> ccmake . gives me:
> 
> 
>  CMAKE_BACKWARDS_COMPATIBILITY    2.4
>  CMAKE_BUILD_TYPE
>  CMAKE_INSTALL_PREFIX             /usr/local
>  ENABLE_TOOLS                     ON
>  ENABLE_TRACE                     ON
>  EXECUTABLE_OUTPUT_PATH
>  LIBRARY_OUTPUT_PATH
>  LIBSYNCML_BIN_DIR                /usr/local/bin
>  LIBSYNCML_DATA_DIR               /usr/local/share
>  LIBSYNCML_EXEC_INSTALL_DIR       /usr/local/bin
>  LIBSYNCML_INCLUDE_DIR            /usr/local/include/libsyncml-1.0
>  LIBSYNCML_LIBRARIES_DIR          /usr/local/lib
>  LIB_SUFFIX
> 
> which to be honest is beyond my understanding ...
> 
> I do have openobex - I believe:
> 
> root@feisty:~/libsyncml/build# dpkg -l | grep -i openobex
> ii  libopenobex1                 1.3-3 OBEX protocol library
> ii  libopenobex1-dev             1.3-3 OBEX protocol library - 
> development files
> root@feisty:~/libsyncml/build#
> 
> Files for example:
> 
> root@feisty:~/libsyncml# dpkg -L libopenobex1-dev
> /.
> /usr
> /usr/share
> /usr/share/doc
> /usr/share/doc/libopenobex1-dev
> /usr/share/doc/libopenobex1-dev/changelog.gz
> /usr/share/doc/libopenobex1-dev/openobex.sgml.gz
> /usr/share/doc/libopenobex1-dev/openobex
> /usr/share/doc/libopenobex1-dev/openobex/index.html
> ...
> /usr/include
> /usr/include/openobex
> /usr/include/openobex/obex.h
> /usr/include/openobex/obex_const.h
> /usr/lib
> /usr/lib/libopenobex.a
> /usr/lib/pkgconfig
> /usr/lib/pkgconfig/openobex.pc
> /usr/lib/libopenobex.so
> 
> Obviously I'm still missing the point ...
> 
> Kind regards
> 
> Gerd
> 
> 


-- 
------------------------------------------------------------------------
Gerd Bavendiek                                  Linux Users check out:
ger...@go...                 http://linos.wordpress.com
------------------------------------------------------------------------