[cfe-dev] Windows 'Roadmap'

Francois Pichet pichet2000 at gmail.com
Sun Jun 5 10:55:23 PDT 2011


On Sun, Jun 5, 2011 at 10:18 AM, Joshua Boyce
<raptorfactor at raptorfactor.com> wrote:
> Is thee a roadmap or timeline anywhere for improved Clang on Windows
> support? I know Clang can build C++ applications on Windows, however afaik
> it can't yet parse the Windows SDK headers, nor can it parse the Dinkumware
> STL headers (though, the latter wouldn't be a big deal if lib++ supported
> Windows... Is there a timeline/roadmap for it too??).
> I understand these things take time, and I appreciate the amount of work
> involved, but both Windows SDK support and STL support are pretty critical
> to actually using Clang to build real-world Windows software, so any
> information I could get would be great.
> Thanks in advance.

Hi, I implemented a bunch of MSVC extensions in the past few months
and I continue to do so in the future.

clang can parse the Windows SDK (v7.0A) here.
As for the MSVC STL code. There are 3 remaining issues (not trivial one):

MSVC 2008 STL:
  - some missing typename

MSVC 2010 STL:
  - template function explicit specialization at class scope
  - Unqualified lookup into dependent bases of class templates

I plan to address those issues in upcoming patches. ( I am currently
suffering with explicit specialization at class scope).  But I don't
have a schedule, clang is just an open source hobby to me.

Also clang can build windows C++ code but it cannot link with the MSVC
C++ standard lib.

When most of the major MSVC parsing are resolved, my roadmap is to
build a kind of MSVC-Clang plugin that will allow calling clang from
within MSVC or from the command line as in:

msvc_clang MyProject.sln MyWarningList.txt

Where MyWarningList.txt is a text file that contains a list of warning
flags to check the source against.
As such my focus will be on using clang as a frontend for warnings and
static analyzing on Windows (not to build binary)

As for generating binaries on Windows, I'll let other people annonce their plan.



More information about the cfe-dev mailing list