WIP: Add CastXML infrastructure.

[thewtex]

Infrastructure to add CastXML [1] support as a parser. It is based of
the GCC-XML parser infrastructure. CastXML is a Clang-based replacement for
GCC-XML.

More changes are required to make the test suite pass.

[1] https://github.com/CastXML/CastXML

[scopatz]

Thanks @thewtex! I'll try playing around with this to make it pass the test suite.

[scopatz]

But also, if anyone else wants to pick this up that'd be awesome!

[empyrical]

Gonna take a stab and see if I can help!

Also, here's a handy link with prebuilt binaries of CastXML for Mac, Linux and Windows so you don't need to go through the effort of compiling it yourself:

http://midas3.kitware.com/midas/folder/13152

[empyrical]

Created a pull request to your pull request! thewtex#1

Adds another commandline option to castxml.

[empyrical]

Also @scopatz I don't understand the internals of XDress enough yet to say, but would it be acceptable if PyGCCXML was used for parsing instead of the hand rolled parser? Would be handy, as it supports castxml now.

[scopatz]

Hi @empyrical! Thanks for taking a stab at this! Sorry for my delayed reply. And yes, it is acceptable to move to PyGCCXML. That project did not exist (If I remember my dates correctly) when the bulk of xdress was written.

[scopatz]

Anything that improves this project, I am all for and happy to help support.

[empyrical]

Awesome! BTW, do you know which version of Linux or Mac OS you were using when the gccxml tests in the current unmodified XDress passed? I haven't been able to get that working properly yet and they fail mid compilation

[scopatz]

I don't remember exactly. It is probably Ubuntu 12.04 - 13.04, and I think that it was gcc 4.6, 4.7, 4.8. I never worked on mac, personally.

[empyrical]

Thanks! Gave that a go (had vms of both 12 and 13) and all had the same error when compiling the discovery example:

[ 28%] Built target basics
[ 35%] Compiling Cython CXX source for cppproj_extra_types...
Scanning dependencies of target cppproj_extra_types
[ 42%] Building CXX object cppproj/CMakeFiles/cppproj_extra_types.dir/cppproj_extra_types.cxx.o
Linking CXX shared module cppproj_extra_types.cpython-35m-x86_64-linux-gnu.so
[ 42%] Built target cppproj_extra_types
[ 50%] Compiling Cython CXX source for discovery...
Scanning dependencies of target discovery
[ 57%] Building CXX object cppproj/CMakeFiles/discovery.dir/discovery.cxx.o
/home/ubuntu/dev/xdress/tests/cppproj/build/cppproj/discovery.cxx:569:97: error: ‘digital_love’ in namespace ‘cppproj’ does not name a type
/home/ubuntu/dev/xdress/tests/cppproj/build/cppproj/discovery.cxx:1635:97: error: ‘digital_love’ in namespace ‘cppproj’ does not name a type

(got the same err with 2.7)

Will have to check out what's going on later when I have more time. Merry xmas!

[empyrical]

Hmm, do you know which version of Cython the tests last passed with? Maybe something changed in Cython

[scopatz]

I do not, sadly. Probably around 0.19 or so.

[empyrical]

Gave it a go with Cython 0.20 and it works great! My suspicion is that the PEP8 Names feature works in some way that works differently in later Cython versions. I'll take a crack at getting pygccxml ported over first, then I'll see what on Earth is goin' on there after that 😄

[scopatz]

Haha OK great!