Hi Marcel,

Am Mittwoch 27 Mai 2009 16:40:50 schrieb Marcel Holtmann:
> I don't understand it. We have to bump the soname. I don't care what
> version you call the package/library, but for Unix/Linux linking purpose
> we have to have a different soname.

To be more clear:
Using autotools to build result in:
  libopenobex.so -> libopenobex.so.2 (SONAME) -> libopenobex.so.2.0.0
and with cmake:
  libopenobex.so -> libopenobex.so.2 (SONAME) -> libopenobex.so.1.6.0

So both have the same SONAME :)

> > > I also started fixing out screwed up declarations overload. Hope that
> > > works now as expected.
> >
> > Let me test those changes for the Win32 build before release, please!
> > It might needs other changes. I will tell you when I'm done with this.
>
> Sure. Let me know when you have verified it.
>
> > > It fixes all built warnings except these two:
> > >
> > > /bin/sh ../libtool --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.
> > >  -I.. -I../include   -fvisibility=hidden  -Wall -O2
> > > -D_FORTIFY_SOURCE=2 -Werror -Wextra -Wno-unused-parameter
> > > -Wno-missing-field-initializers -Wdeclaration-after-statement
> > > -Wmissing-declarations -Wredundant-decls -Wcast-align
> > > -D_FORTIFY_SOURCE=2 -MT libopenobex_la-obex.lo -MD -MP -MF
> > > .deps/libopenobex_la-obex.Tpo -c -o libopenobex_la-obex.lo `test -f
> > > 'obex.c' || echo './'`obex.c
> > >  gcc -DHAVE_CONFIG_H -I. -I.. -I../include -fvisibility=hidden -Wall
> > >  -O2 -D_FORTIFY_SOURCE=2 -Werror -Wextra -Wno-unused-parameter
> > > -Wno-missing-field-initializers -Wdeclaration-after-statement
> > > -Wmissing-declarations -Wredundant-decls -Wcast-align
> > > -D_FORTIFY_SOURCE=2 -MT libopenobex_la-obex.lo -MD -MP -MF
> > > .deps/libopenobex_la-obex.Tpo -c obex.c  -fPIC -DPIC -o
> > > .libs/libopenobex_la-obex.o
> > > cc1: warnings being treated as errors
> > > obex.c:1180: error: no previous declaration for ‘BtOBEX_ServerRegister’
> > > obex.c:1207: error: no previous declaration for
> > > ‘BtOBEX_TransportConnect’
> > >
> > > So how do we get rid of these two? I wanna build it with -Werror now.
> >
> > in lib/obex.c:
> > #include "bluez_compat.h"
> >
> > before
> > #include <openobex/obex.h>
>
> That is not it. Seems like Bluetooth support is wrongly enabled or the
> ifdef around SOL_RFCOMM somewhere is messed up.

I do not have this problem, here, though. However, I am still on bluez 3.x. I 
have SOL_RFCOMM defined in bluetooth/bluetooth.h
I fixed some other compiler warnings (not the unsigned vs. signed stuff, only 
the ones in lib/ that make most sense).

HS


------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT 
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, & 
iPhoneDevCamp as they present alongside digital heavyweights like Barbarian 
Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com 
_______________________________________________
Openobex-users mailing list
Openobex-users@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/openobex-users

Reply via email to