[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 12:58:27 PDT 2008

On May 14, 2008, at 12:32 PM, Gordon Henriksen wrote:

> On 2008-05-14, at 15:06, Argiris Kirtzidis wrote:
>> Steve Naroff wrote:
>>> Argiris,
>>> At the moment, we build/test clang using VC++ 2005 (which this  
>>> commit
>>> breaks).
>>> Would it be possible to revert this and have two sets of project
>>> files?
>>> If so, I'd appreciate it. At the moment, I am unable to build on
>>> Windows (and I'm not in a position to upgrade to VC++ 2008).
>> I did the upgrade because the LLVM VC++ projects were upgraded, thus
>> the
>> clang solution couldn't use them without an upgrade.
>> Shall I add two sets of project files for LLVM too ? The 2005 ones
>> getting a '_vc8' postfix ?
> It might make it easier to maintain for Visual Studio upgrades if all
> the Visual Studio files were kept in a single directory, like clang/
> VC8/{clang.sln,*.vcproj} and clang/VC9/{clang.sln,*.vcproj}. This way
> they could be duplicated in a straightforward fashion and upgraded
> without renaming projects or adjusting reference paths.

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...


> — Gordon
> _______________________________________________
> cfe-commits mailing list
> cfe-commits at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits

More information about the cfe-commits mailing list