Am Mittwoch, 29. Juni 2011, 18:39:27 schrieb Iain Hibbert: > Hi > > I just noticed (because I now have openobex-current installed, instead of > 1.5) that obexftp will not actually build.. there has been an API change > with obex_t.. previously it was a pointer "void *" but now it is defined > as a "struct obex" which contents are private to openobex.. > > the problem is that passing around or storing an obex_t is not possible in > client code, since the size of obex_t is not known to the compiler.. > > the correct way to create opaque handles is to do have the typedef as a > pointer, so that the size is known..?
With openobex-git, you _must_ use the code from: https://www.gitorious.org/obexftp The problem is solved there. The right way is to always use a obex_t* (and that''s what you get from the library). HS ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Openobex-users mailing list Openobex-users@lists.sourceforge.net http://lists.sourceforge.net/lists/listinfo/openobex-users
