[cfe-commits] r51101 - in /cfe/trunk/win32: clangAST/clangAST.vcproj clangAnalysis/clangAnalysis.vcproj clangBasic/clangBasic.vcproj clangCodeGen/clangCodeGen.vcproj clangDriver/clangDriver.vcproj clangLex/clangLex.vcproj clangParse/clangParse.vcproj clangRewrite/clangRewrite.vcproj clangSema/clangSema.vcproj

Steve Naroff snaroff at apple.com
Wed May 14 13:56:19 PDT 2008

On May 14, 2008, at 1:41 PM, Chris Lattner wrote:

> On May 14, 2008, at 12:58 PM, Steve Naroff wrote:
>> Makes sense to me.
>> One question (for anyone): Is there actually any advantage to  
>> having VC
>> ++ 2008 project files? (I assume so).
>> If not, I don't see any reason to complicate life (since VC++ 2008
>> must read VC++ 2005 files). The more project files, the larger the
>> maintenance burden...
> If 2008 works with 2005 files, I'd strongly prefer to just have 2005  
> files.  This means that someone that uses 2005 will need to keep  
> them up to date though.

I've been doing this for clang and (occasionally) llvm. I have no  
problem continuing to do this for clang, however it would be good if  
there was someone  (on llvm-dev) doing it for llvm. If nobody in the  
llvm community is using VC++ 2005, then maybe I can update? We can  
discuss offline...


> -Chris

More information about the cfe-commits mailing list