Chandler Carruth
2009-Oct-29 02:35 UTC
[LLVMdev] Any objections to removing 'win32/...' subtree from LLVM?
FYI, I'll plan on removing this subtree on Monday of next week if no one else chimes in requesting a reprieve... On Wed, Oct 28, 2009 at 5:59 PM, PyLLVM <pyllvm at gmail.com> wrote:> No objection. > I'm studying LLVM on Win32 using visual studio. > CMake works well for it. > > > On Oct 26, 7:44 am, Chandler Carruth <chandl... at google.com> wrote: >> 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. >> _______________________________________________ >> LLVM Developers mailing list >> LLVM... at cs.uiuc.edu http://llvm.cs.uiuc.eduhttp://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >
Óscar Fuentes
2009-Nov-06 17:10 UTC
[LLVMdev] Any objections to removing 'win32/...' subtree from LLVM?
Chandler Carruth <chandlerc at 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/ -- Óscar
Chris Lattner
2009-Nov-07 08:32 UTC
[LLVMdev] Any objections to removing 'win32/...' subtree from LLVM?
On Nov 6, 2009, at 9:10 AM, Óscar Fuentes wrote:> Chandler Carruth <chandlerc at 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. -Chris
Apparently Analagous Threads
- [LLVMdev] Any objections to removing 'win32/...' subtree from LLVM?
- [LLVMdev] Any objections to removing 'win32/...' subtree from LLVM?
- [LLVMdev] Any objections to removing 'win32/...' subtree from LLVM?
- [LLVMdev] Any objections to removing 'win32/...' subtree from LLVM?
- fixing a problem in the subtree code