1. Thomas Heller

    Thomas Heller on 10/30/2006 5:21 a.m. #

    Maybe this helps:<br />
    <br />

  2. Thomas Heller

    Thomas Heller on 10/30/2006 9:13 a.m. #

    I should mention that I have *not* tried the above approach myself.<br />
    <br />
    OTOH, some thoughts:<br />
    <br />
    There has been a patch for gccxml posted to the gccxml mailing list which adds support for the VC2003 toolkit (or how was it named; the one that's no longer available from MS).<br />
    <br />
    Since gccxml only needs the header files and not the MS compiler itself, it should (in principle) be possible to adapt it to the freely downloadable MS platform SDKs. Two problems have to be solved:<br />
    1. Find the header files using registry entries<br />
    2. Patch the header files so that gccxml can parse them.

  3. Thomas Heller

    Thomas Heller on 10/31/2006 12:13 p.m. #

    Update: gccxml, in CVS, is able to work together with the free VisualStudio2005 Express edition.<br />
    I'll post a binary installer for gccxml to the ctypes SF download page ASAP.

  4. Mike Fletcher

    Mike Fletcher on 10/31/2006 9:51 p.m. #

    Thanks Thomas. I'll take a look next time I have some OpenGL time.

  5. John Eckhart

    John Eckhart on 11/07/2007 2:16 p.m. #

    Is there a way to bypass the registry checks for GCC-XML? Currently, my team uses a subset of the MS toolchain that we copy from one machine to another which we find necessary to support multiple versions of the MS compiler at one time (and it's much smaller and easier than the full blown MS install). If we set the paths correctly (part of the build process) then the MS tools function normally. Is there any way to pass the path of the MS toolchain to GCC-XML through something OTHER than the registry?

Comments are closed.


Pingbacks are closed.