As discussed in IRC, nevermind this. I misread the header files.
On 4 August 2014 01:12, Auke Booij <[email protected]> wrote: > On 30 July 2014 20:27, Pekka Paalanen <[email protected]> wrote: >> Actually no. Binding writers are expected to write their own code >> generator for their language, like wayland-scanner is for C. You >> are expected to not use the static inline generated C functions. >> >> All the static inline functions are not part of the... how was it >> defined, ABI? Inline functions obviously get compiled into the app, >> not exported by the library. > > what about the wl_interface structs? they are exposed by the > wayland-*-protocol.h files, so presumably off-limits, but opaque > structs otherwise (the definition in wayland-util.h is deprecated), so > I can't create my own wl_interface structs. > > hence, what am I supposed to pass to wl_proxy_marshal_constructor ? _______________________________________________ wayland-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-devel
