Displaying 3 results from an estimated 3 matches for "r86358".
2009 Nov 07
1
[LLVMdev] Any objections to removing 'win32/...' subtree from LLVM?
...ordance? 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
2009 Oct 29
2
[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:
>>
2009 Nov 06
0
[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