On 4/25/08, Adam Bark <[EMAIL PROTECTED]> wrote: > 2008/4/24 Adam Bark <[EMAIL PROTECTED]>: > > > Hi I'm trying to wrap pulseaudio with wrap.py using this command works ok > mostly: > > > > pyglet/tools/wraptypes/wrap.py -lpulse -olibpulse.py > /usr/include/pulse/mainloop-api.h > /usr/include/pulse/sample.h /usr/include/pulse/def.h > /usr/include/pulse/context.h /usr/include/pulse/stream.h > /usr/include/pulse/introspect.h /usr/include/pulse/subscribe.h > /usr/include/pulse/scache.h /usr/include/pulse/version.h > /usr/include/pulse/error.h /usr/include/pulse/channelmap.h > /usr/include/pulse/operation.h /usr/include/pulse/volume.h > /usr/include/pulse/xmalloc.h /usr/include/pulse/utf8.h > /usr/include/pulse/thread-mainloop.h > /usr/include/pulse/mainloop.h /usr/include/pulse/util.h > /usr/include/pulse/timeval.h > /usr/include/pulse/mainloop-signal.h > > > > > > but there seems to be some functions missing such as everything defined in > > context.h. I tried running wrap.py with just context.h and it seems to > work fine. > > What's the deal? Should I just copy over the output from the context.h > only run > > into the main wrapper? > > Ok more strangeness I tried putting context.h at a different point in the > list and it > included all the stuff from it this time :s >
Yeah, wrap.py is fairly buggy. I make a point never to fix any of it when there's a workaround ;-) Alex. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en -~----------~----~----~----~------~----~------~--~---
