I'm using the amd64_x86 toolchain. They're supposed to be identical so that's unlikely to be the problem, but it's the only difference i can see. Let me know what happens on your clean rebuild On Fri, Mar 18, 2016 at 7:56 AM Cameron <came...@moodycamel.com> wrote:
> cameron314 added a comment. > > Since it works without my patch, you're probably right about it being > related to the UNICODE define. All the other changes are completely removed > from that part of the code. But I still don't see how it could affect that. > > Here's the script I use to run cmake: > > setlocal > set > PATH=%ProgramFiles%\Ninja;%ProgramFiles(x86)%\CMake\bin;%SYSTEMROOT%\system32;%SYSTEMROOT%;%SWIGDIR% > call "%VS140COMNTOOLS%\vsvars32.bat" > mkdir VS2015Debug > cd VS2015Debug > cmake -G "Ninja" -DLLVM_BUILD_EXAMPLES:BOOL=false > -DPYTHON_HOME="C:\Python35" -DLLDB_DISABLE_PYTHON:BOOL=false > -DLLDB_TEST_COMPILER=%cd%\bin\clang.exe -DCMAKE_BUILD_TYPE=Debug .. > cd .. > mkdir VS2015Release > cd VS2015Release > cmake -G "Ninja" -DLLVM_BUILD_EXAMPLES:BOOL=false > -DPYTHON_HOME="C:\Python35" -DLLDB_DISABLE_PYTHON:BOOL=false > -DLLDB_TEST_COMPILER=%cd%\bin\clang.exe -DCMAKE_BUILD_TYPE=Release .. > cd .. > endlocal > > This is with VS2015 update 1. And it's already the x86 version, the patch > has diverged significantly from what we have locally (which is based on a > snapshot from several weeks ago) so I've been using the tip as-is :-) > > I'm trying a fresh Debug build from scratch (deleting and re-creating the > cmake build folder). I'll report back when it's done. > > > http://reviews.llvm.org/D17107 > > > >
_______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
