Thread: [pygccxml-development] __int128_t traceback
Brought to you by:
mbaas,
roman_yakovenko
From: Gustavo C. <gjc...@gm...> - 2010-07-06 14:05:12
|
It seems pygccxml (1.0) tracbacks when the type __int128_t is found in a header file. I don't really care about the type, it is used internally by an implementation class which I do not wish to wrap, but the mere presence of this type is enough to crash pygccxml and stop me from scanning the rest of the API. File "/home/tomh/hg/jul10/ns-3-allinone/pybindgen/pybindgen/gccxmlparser.py", line 683, in parse_init self.declarations = parser.parse(header_files, self.gccxml_config) File "/usr/lib/python2.5/site-packages/pygccxml/parser/__init__.py", line 50, in parse self.declarations = parser.parse(header_files, self.gccxml_config) File "/usr/lib/python2.5/site-packages/pygccxml/parser/__init__.py", line 50, in parse answer = parser.read_files(files, compilation_mode) File "/usr/lib/python2.5/site-packages/pygccxml/parser/project_reader.py", line 225, in read_files answer = parser.read_files(files, compilation_mode) File "/usr/lib/python2.5/site-packages/pygccxml/parser/project_reader.py", line 225, in read_files return self.__parse_file_by_file(files) File "/usr/lib/python2.5/site-packages/pygccxml/parser/project_reader.py", line 250, in __parse_file_by_file decls = reader.read_file( header ) File "/usr/lib/python2.5/site-packages/pygccxml/parser/source_reader.py", line 197, in read_file return self.__parse_file_by_file(files) File "/usr/lib/python2.5/site-packages/pygccxml/parser/project_reader.py", line 250, in __parse_file_by_file decls = reader.read_file( header ) File "/usr/lib/python2.5/site-packages/pygccxml/parser/source_reader.py", line 197, in read_file return self.read_gccxml_file( source_file ) File "/usr/lib/python2.5/site-packages/pygccxml/parser/source_reader.py", line 224, in read_gccxml_file raise error RuntimeError: pygccxml error: unable to find fundamental type with name '__int128_t'. return self.read_gccxml_file( source_file ) File "/usr/lib/python2.5/site-packages/pygccxml/parser/source_reader.py", line 224, in read_gccxml_file raise error RuntimeError: pygccxml error: unable to find fundamental type with name '__int128_t'. -- Gustavo J. A. M. Carneiro INESC Porto, UTM, WiN, http://win.inescporto.pt/gjc "The universe is always one step beyond logic." -- Frank Herbert |
From: Roman Y. <rom...@gm...> - 2010-07-06 18:50:06
|
On Tue, Jul 6, 2010 at 5:04 PM, Gustavo Carneiro <gjc...@gm...> wrote: > It seems pygccxml (1.0) tracbacks when the type __int128_t is found in a > header file. I don't really care about the type, it is used internally by > an implementation class which I do not wish to wrap, but the mere presence > of this type is enough to crash pygccxml and stop me from scanning the rest > of the API. I understand. We have few ways to continue: * you create an xml file that contains that type and send it to me and I fix pygccxml * you can add that type to pygccxml by yourself and send me the patches :-) Basically the are only few place, where pygccxml should be changed: * declarations/cpptypes.py * Python class, that represents the type should be created and added to the FUNDAMENTAL_TYPES dictionary * declarations/type_traits.py * is_integral function should be changed to return "true" for this type too * declarations/__init__.py * the file should provide access to the class That's all. You are free to select any method you want :-) -- Roman Yakovenko C++ Python language binding http://www.language-binding.net/ |
From: Gustavo C. <gjc...@gm...> - 2010-07-16 14:50:36
Attachments:
int128.diff
|
Here's the patch as promised. Best regards. On Tue, Jul 6, 2010 at 19:49, Roman Yakovenko <rom...@gm...>wrote: > On Tue, Jul 6, 2010 at 5:04 PM, Gustavo Carneiro <gjc...@gm...> > wrote: > > It seems pygccxml (1.0) tracbacks when the type __int128_t is found in a > > header file. I don't really care about the type, it is used internally > by > > an implementation class which I do not wish to wrap, but the mere > presence > > of this type is enough to crash pygccxml and stop me from scanning the > rest > > of the API. > > I understand. > > We have few ways to continue: > * you create an xml file that contains that type and send it to me and > I fix pygccxml > * you can add that type to pygccxml by yourself and send me the patches :-) > > > Basically the are only few place, where pygccxml should be changed: > * declarations/cpptypes.py > * Python class, that represents the type should be created and added > to the FUNDAMENTAL_TYPES dictionary > * declarations/type_traits.py > * is_integral function should be changed to return "true" for this type > too > * declarations/__init__.py > * the file should provide access to the class > > That's all. You are free to select any method you want :-) > > > > -- > Roman Yakovenko > C++ Python language binding > http://www.language-binding.net/ > -- Gustavo J. A. M. Carneiro INESC Porto, UTM, WiN, http://win.inescporto.pt/gjc "The universe is always one step beyond logic." -- Frank Herbert |
From: Roman Y. <rom...@gm...> - 2010-07-19 06:42:40
|
On Fri, Jul 16, 2010 at 5:50 PM, Gustavo Carneiro <gjc...@gm...> wrote: > Here's the patch as promised. > Best regards. Thank you. Your patch was integrated: http://pygccxml.svn.sourceforge.net/pygccxml/?rev=1844&view=rev . -- Roman Yakovenko C++ Python language binding http://www.language-binding.net/ |