Any objections to removing 'win32/...' subtree from LLVM?

Daniel Dunbar tells me it's no longer in use, and poking around shows
that it is extremely out of sync with trunk source code.

No objection.
I'm studying LLVM on Win32 using visual studio.
CMake works well for it.

FYI, I'll plan on removing this subtree on Monday of next week if no
one else chimes in requesting a reprieve...

Chandler Carruth <chandlerc@google.com> writes:

FYI, I'll plan on removing this subtree on Monday of next week if no
one else chimes in requesting a reprieve...

The Visual C++ project files are still there.

Anyone objected by private e-mail? Can we know the reasons just in case
we can enhance the cmake build on accordance? In the past, the only
reason for not removing win32/ was that the cmake-generated project
files are not relocatable. As the win32/ project files seem out of date
for months now, I reckon that the user who had that requirement switched
to cmake.

The mere existence of the win32/ subtree is a source of confussion for
newcomers.

Maybe the same applies to Xcode/

Removed in r86358. I don't know what happened to Chandler.

-Chris

Chandler Carruth <chandlerc@google.com> writes:

FYI, I'll plan on removing this subtree on Monday of next week if no
one else chimes in requesting a reprieve...

The Visual C++ project files are still there.

Anyone objected by private e-mail? Can we know the reasons just in
case
we can enhance the cmake build on accordance? In the past, the only
reason for not removing win32/ was that the cmake-generated project
files are not relocatable. As the win32/ project files seem out of
date
for months now, I reckon that the user who had that requirement
switched
to cmake.

Removed in r86358. I don't know what happened to Chandler.

Sorry, fires broke out this week. Was going to do it this weekend, but
you got there first.