Libiphone libiphone

Comments and changes to this ticket

• 

  Jonathan Beck October 26th, 2009 @ 07:08 AM

  • State changed from “new” to “open”
  • Tag set to “libplist”
  • Assigned user set to “Jonathan Beck”

  Someone on the mailing list have experienced the same behavior so it is probably a bug.

  Can you attach the generated swig/plistPYTHON_wrap.cxx file so I can see what is wrong.

  cheers.

• You flagged this item as spam.
  

  pki October 26th, 2009 @ 07:20 AM

  sure ;-)

  • plistpython_wrap.cxx 427.6 KB
• 

  Jonathan Beck October 26th, 2009 @ 05:45 PM

  Thanks,

  Apparently some definitions changed between SWIG 1.3.36 and 1.3.37.
  It should be fixed in the git repository.

  Can you report if it works and close this ticket if it does ?
  I'll make a new release then.
  Thanks for reporting this issue :)

  cheers.

• You flagged this item as spam.
  

  pki October 26th, 2009 @ 07:04 PM

  Hi Jonathan

  I still have that problem with newest source. It looks that the following warnings cause it:

  /home/pki/Downloads/libplist/include/plist/Utils.h:34: Warning(314): 'in' is a python keyword, renaming to 'in' /home/pki/Downloads/libplist/include/plist/Utils.h:34: Warning(314): 'in' is a python keyword, renaming to 'in' /home/pki/Downloads/libplist/include/plist/Utils.h:34: Warning(314): 'in' is a python keyword, renaming to '_in'

  swig is invoked from makefile with '-Werror', so that target fails to build. Once I changed parameter names in Utils.h, lines 34 and 35 to something else than 'in' I managed to complete the build :-), so I think we can close that ticket.

  Regards,

  Piotr

• 

  Jonathan Beck October 29th, 2009 @ 01:02 PM

  • State changed from “open” to “resolved”