<div style="text-align: left;" id="result_box" dir="ltr">Brad,<br><br><br>Okay, no problem, when solved let me know. thank you very much.<br><br><br><br>Regards,<br>Paulo Amorim<br><br><br></div><br><br><div class="gmail_quote">
2009/2/5 Brad King <span dir="ltr"><<a href="mailto:brad.king@kitware.com">brad.king@kitware.com</a>></span><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">Paulo Henrique Junqueira Amorim wrote:<br>
</div><div class="Ih2E3d"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Apply the patch in CableSwig but still with errors. Attached is the log.<br>
</blockquote>
<br></div>
Okay, it looks like the GCC parser itself inside gccxml does not work when built 64-bit. I'll investigate this, but it may take a while.<br>
<br>
For now, use my original workaround suggestion of building CableSwig in 32-bit mode. You can still use it for a 64-bit ITK.<br>
<br>
-Brad<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
2009/2/5 Brad King <<a href="mailto:brad.king@kitware.com" target="_blank">brad.king@kitware.com</a> <mailto:<a href="mailto:brad.king@kitware.com" target="_blank">brad.king@kitware.com</a>>><div class="Ih2E3d">
<br>
<br>
Brad King wrote:<br>
<br>
Paulo Henrique Junqueira Amorim wrote:<br>
<br>
20>Compiler "C:/Program Files (x86)/Microsoft Visual Studio<br>
9.0/VC/bin/amd64/cl.exe" is not supported by GCC_XML because<br>
none of MSVC 6, 7, 7.1, 8 is installed.<br>
<br>
<br>
There is a bug in this error message. It should be looking for<br>
Vc9 too. I'll fix that.<br>
<br>
I think the real problem is that 64-bit gccxml does not look in<br>
32-bit registry entries, so it does not see the VS installation.<br>
This is an issue with the way MS implements support for both<br>
64-bit and 32-bit applications. An application without<br>
knowledge of the mechanism only sees registry entries for<br>
applications built with the same 'bitness'. I'm working on a fix<br>
to teach gccxml where to look.<br>
<br>
<br>
I've attached a patch which should fix this.<br>
<br>
-Brad<br>
<br>
<br>
</div></blockquote>
<br>
</blockquote></div><br>