[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

Argiris Kirtzidis akyrtzi at gmail.com
Wed May 14 13:55:02 PDT 2008

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.

Unfortunately VC++ 2008 doesn't work with 2005 files without an upgrade.

Gordon Henriksen wrote:
> 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.

Keeping VC8/VC9 builds in separate directories is a good idea, but I'd 
prefer that vcprojs are in separate directories (as it is now) so that 
obj files can be put in the project's directory.

I suggest keeping the win32 directory structure but:

-Have "win32-vc8" and "win32-vc9" directories for llvm and clang.
-Move "clang.sln" out of llvm/win32 and into clang/win32

Is everyone ok with this ?


More information about the cfe-commits mailing list