[Insight-users] Re: ITK Wrappers and gcc_xml
Charl P. Botha
cpbotha at cpbotha.net
Wed Feb 15 18:24:06 EST 2006
On 2/15/06, Brad King <brad.king at kitware.com> wrote:
> > Regardless of that, the WrapITK wrappers that Gaetan and I have been
> > working on does attempt to wrap compiler-generated code. Thus, I would
> > love to be able to figure out a reliable way to configure gcc_xml to
> > emulate whatever compiler is selected in/by cmake. Does anyone have any
> > ideas?
>
> In the GCCXML_CREATE_XML_FILE macro the command line for gcc-xml is
> constructed. The include path is loaded via a file specified by the
> --gccxml-gcc-options argument. You can add the argument
> --gccxml-compiler to specify the name of the compiler to simulate. For
> most generators the value of ${CMAKE_CXX_COMPILER} can be used. For
> Visual Studio generators one should use "msvc6", "msvc7", "msvc71", or
> "msvc8" to make sure the proper VS version is simulated. Read the man
> page of gccxml (or gccxml --help) for more settings used to tune the
> simulation.
Just to make 100% sure, I added --gccxml-compiler msvc71 (which is the
vs.net 2003 that I use) to the GCCXML_CREATE_XML_FILE macro in
CreateWrapperLibrary.cmake of my WrapITK checkout and rebuilt the
whole thing. I still get exactly the same errors:
c:\build\WrapITK-VS71\CommonA\wrap_ITKCommonBasePython.cxx(3833):
error C2664: 'itk::MultiThreader::SetMultipleMethod' : cannot convert
parameter 2 from 'unsigned long (__cdecl *)(void *)' to
'itk::ThreadFunctionType'
... and so forth.
More information about the Insight-users
mailing list