When we move to VS 2015 (which will be soon, btw) we will require Python
3.5+ on Windows. This already works for the most part, you can even try it
out today. I've spent the better part of the past 6 months making LLDB's
python bindings work with Python 3. The best part is that you don't need
to
>
> VS 2013 support is going to be deprecated soon. At that point it could
break any time, because nobody is going to be making an effort to keep it >
> working.
>
How is this going to play with Python scripting on Windows? Given
that LLDB only supports Python 2.7 bindings,
and that Python 2.7
VS 2013 support is going to be deprecated soon. At that point it could
break any time, because nobody is going to be making an effort to keep it
working.
On Tue, Jan 12, 2016 at 7:54 AM Aidan Dodds via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> Just to chip in on this thread.
> I regularly bui
Just to chip in on this thread.
I regularly build X64 LLDB using Visual Studio, but I only use it for
debugging remote targets.
I have noticed the gtests linking error, but unfortunately due to tight
time constraints I've not been free to fix it.
I tend to 'unload' all of the projects in Visual
thanks for workaround
2016-01-11 21:48 GMT+03:00 Zachary Turner :
> Yea, unfortunately the way things work is that the person who is affected
> by the problem and who needs it fixed is usually the one that needs to fix
> it. Right now we don't have any Windows people building inside Visual
> Stu
Yea, unfortunately the way things work is that the person who is affected
by the problem and who needs it fixed is usually the one that needs to fix
it. Right now we don't have any Windows people building inside Visual
Studio, so nobody has fixed that. But you're welcome to submit a patch :)
FWI
thanks. i build successefuly llvm and lldb with ninja and cl compiler.
If i build VS solution without options on CMake then i have ever more
errors around unittests in llvm.
like that:
"d:\code\llvm\build\LLVM.sln" (целевой объект по умолчанию) (1) ->
"d:\code\llvm\build\unittests\ADT\ADTTests.v
I have never built with -DLLVM_INCLUDE_TESTS=OFF
-DCLANG_INCLUDE_EXAMPLES=OFF -DCLANG_INCLUDE_TESTS=OFF before, so that
could be related. Can you try removing those options on CMake to see if
that fixes it?
The other thing I do differently is I use ninja generator. So I use -G
Ninja instead of -
thanks.
i still have 5 errors while linking
"d:\code\llvm\build\LLVM.sln" (целевой объект по умолчанию) (1) ->
"d:\code\llvm\build\tools\lldb\unittests\LLDBUnitTests.vcxproj.metaproj"
(целев
ой объект по умолчанию) (741) ->
"d:\code\llvm\build\tools\lldb\unittests\Utility\UtilityTests.vcxproj.metap
Should look like this:
llvm
|__ tools
|__ clang
|__ lld
|__ lldb
You will need clang because lldb needs to link against it, and you will
need lld because lldb on Windows doesn't (yet) understand PDB, so you have
to compile your programs with clang.exe -fuse-ld=lld
On Sat, Jan 9,
If i want compile as part of llvm then what is destination directory for
lldb trunk sources ?
I has placed this in llvm/projects/lldb and has much errors while
compiling lldb with MSVC 2015.
"d:\code\llvm\build\LLVM.sln" (целевой объект по умолчанию) (1) ->
"d:\code\llvm\build\ALL_BUILD.vcxproj.m
11 matches
Mail list logo
