[cfe-dev] win32/llvm.sln, win32/clang.sln

[Óscar Fuentes]

"Nicolas Capens" <nicolas at capens.net> writes:

> The Visual Studio solution and project files are quite handy. CMake creates
> absolute paths instead of relative paths, making it cumbersome to move
> things around. Also, for newcomers (e.g. students) it's really great to be
> able to download the package, open the solution and compile without any
> complication.
>
> They haven't been updated in a while, but it would be nice to have working
> ones in the 2.5 release...

There is a contradiction among this two paragraphs: the first one says
"they are convenient" and the second one says "they are outdated".

The primary goal of the LLVM CMake build system was to alleviate
maintenance work, the second was to support all VS versions wich are C++
compliant enough to compile LLVM. Another nice side-effect is that now
VS users can build all LLVM targets. The VS project files under win32/
are good enough as far as someone maintains them, you have the correct
VS version and don't need the missing functionality.

Finally, a student that works with LLVM is not a computer newbie: he
knows how to follow web links, install a piece of software, and
copy/paste onto a console. This process requires less time than the LLVM
build itself.

Of course, this requires that the LLVM CMake instructions should become
integrated into the LLVM docs. I hope to do this before the 2.5 release.

-- 
Oscar