[C++-sig] To Spicy For Py++ [was: A wrapped class contains another wrapped class. Hilarity ensues.]

[Jason Kankiewicz]

Scott,
  I, too, had difficulty getting GCC_XML to grok MSVC8 code early this 
year. Fortunately, the CVS version soon contained new headers and my 
problems disappeared. The problems existed because I had installed 
Service Pack 1 for VS2005 and GCC_XML's VC8 headers hadn't yet been 
modified to match.
 
  Have you installed Service Pack 1 for VS2005? If not, I suggest that 
you do.

Regards,
Jason

Scott VanSickle wrote:
> If you can get Py++ to work with the VS2005 headers please email the group.  I spent well over a solid week to try to generate my wrapper classes with that method and gave up (it sounds like you had the same pleasant experience).  I made dummy versions of any VC2005 headers that had errors, set every #define I could find to try to make GCC-XML happy and basically got nowhere.  I was not trying to wrap any of my own template code (except STL and some boost stuff) and still failed with trying to wrap even a pretty minimal class.  It is obvious to me that the VC2005 headers are just not intended by the authors to be used from anything but VC2005.  I also had many issues with the boost libraries; I probably could have worked around those in my case.
>
> Scott V
>
>
>
> From: c++-sig-bounces at python.org [mailto:c++-sig-bounces at python.org] On Behalf Of Matthew Scouten
> Sent: Tuesday, November 27, 2007 5:28 PM
> To: Development of Python/C++ integration
> Subject: Re: [C++-sig] To Spicy For Py++ [was: A wrapped class contains another wrapped class. Hilarity ensues.]
>
>
> On Nov 27, 2007 2:06 PM, Roman Yakovenko <roman.yakovenko at gmail.com> wrote:
> On Nov 27, 2007 9:59 PM, Matthew Scouten <matthew.scouten at gmail.com> wrote:
>   
>> We did try that. GCC-XML chokes on our library code. It was originally
>> written for C,  and later ported to C++.  Along the way it picked up some
>> crazy preprocessor and template hacks and even some meta-template
>> programming. Granted most of this stuff is not the part we need to wrap, but
>> it is not easily separable. On top of all that, it was written with msvc8 in
>> mind, not GCC.
>>
>> Even with with options set to emulate msvc8, GCC-XML generates hundreds of
>> error messages the last of which is "internal compiler error". It works fine
>> on other code, and our library compiles just fine on msvc8.
>>     
> :-(. Did you try new latest cvs version of gccxml? It is built on top
> of GCC 4.2.
> SVN version of Py++ and pygccxml should work fine with it.
>
> 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.
>
> 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.
>