(good catch :-) )
On Wed, Nov 18, 2015 at 1:20 PM, Todd Fiala wrote:
> Nope, I'm wrong. Sorry!
>
> On Wed, Nov 18, 2015 at 1:15 PM, Todd Fiala wrote:
>
>> I don't *think* that's right? (At least, not for Linux).
>>
>> It's not coming from the source dir. It gets generated into the binary
>>
Nope, I'm wrong. Sorry!
On Wed, Nov 18, 2015 at 1:15 PM, Todd Fiala wrote:
> I don't *think* that's right? (At least, not for Linux).
>
> It's not coming from the source dir. It gets generated into the binary
> directory. Or - maybe the Windows ones write the output into the source
> tree?
I don't *think* that's right? (At least, not for Linux).
It's not coming from the source dir. It gets generated into the binary
directory. Or - maybe the Windows ones write the output into the source
tree? Do we need to conditionalize the location of lldb.py based on the
build?
-Todd
On Wed,
Author: zturner
Date: Wed Nov 18 15:09:55 2015
New Revision: 253501
URL: http://llvm.org/viewvc/llvm-project?rev=253501&view=rev
Log:
Fix CMake dependency on lldb.py
Modified:
lldb/trunk/CMakeLists.txt
Modified: lldb/trunk/CMakeLists.txt
URL:
http://llvm.org/viewvc/llvm-project/lldb/trunk/C
