I'm not using the standalone build on Windows, i just suffer through opening a mega solution. Reid did some work recently to make it better, but it still doesn't totally support anyone's needs.
The main motivation for having a standalone build is that it's a necessary (but not necessarily sufficient) precursor to having a usable xcode solution, which is itself a necessary (but again perhaps not sufficient) precondition to moving towards a single build system. I'm not versed enough in the LLVM core shared CMake infrastructure, but I envision a world where supporting a standalone build requires almost 0 project specific CMake code. Sadly, achieving that seems quite difficult On Sun, Dec 28, 2014 at 7:22 AM Chandler Carruth <chandl...@gmail.com> wrote: > I thought that Zach was on Windows, but I would be surprised as I can't > get it to work with an installed Clang. It errors in the cmake step, unable > to find some cmake module. > > Is anyone genuinely trying to support this CMake configuration? It adds > quite a bit of complexity. If so, could they fix this error or suggest how > to fix it on the Clang side? (I help maintain the Clang cmake build, so I'm > happy to enact any reasonable changes needed...) > > This came up because I have a change to the LLDB CMake build but am > currently unable to test it in a fully standalone build (IE, w/o a source > tree). > > -Chandler > _______________________________________________ > lldb-dev mailing list > lldb-dev@cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev >
_______________________________________________ lldb-dev mailing list lldb-dev@cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
