<br><br><div class="gmail_quote">On Nov 27, 2007 2:06 PM, Roman Yakovenko <<a href="mailto:roman.yakovenko@gmail.com">roman.yakovenko@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Nov 27, 2007 9:59 PM, Matthew Scouten <<a href="mailto:matthew.scouten@gmail.com">matthew.scouten@gmail.com</a>> wrote:<br></div><div class="Ih2E3d">> We did try that. GCC-XML chokes on our library code. It was originally
<br>> written for C, and later ported to C++. Along the way it picked up some<br>> crazy preprocessor and template hacks and even some meta-template<br>> programming. Granted most of this stuff is not the part we need to wrap, but
<br>> it is not easily separable. On top of all that, it was written with msvc8 in<br>> mind, not GCC.<br>><br>> Even with with options set to emulate msvc8, GCC-XML generates hundreds of<br>> error messages the last of which is "internal compiler error". It works fine
<br>> on other code, and our library compiles just fine on msvc8.<br><br></div>:-(. Did you try new latest cvs version of gccxml? It is built on top<br>of GCC 4.2.<br>SVN version of Py++ and pygccxml should work fine with it.
</blockquote><div><br>Yes, when we started a couple of months ago we got it fresh from cvs. I had to get it at home and carry it in on a flashdrive because some fire wall between here and there prevented me from pulling down at work. Then I had to get Cmake and get the Dad-Blasted thing to compile. Then I had to find the right options to beat it with to get it to work on simple example code. Finally, I point it at our library and what does it do? It blows up in my face.
<br><br>If there has been a major update in the past 2 or 3 months, it might be worth checking out again. otherwise I am not throwing any more time down that rabbit hole.<br></div></div><br>