On 22/11/2019 01:26, Adrian McCarthy wrote:
Yes, that sounds plausible, but I don't recall for sure. I think
there's a build-time option to say you don't want Python at all, but I
can't remember if there was a load-as-needed option.
I'm pretty sure we have never had explicit support for anyth
Yes, that sounds plausible, but I don't recall for sure. I think there's a
build-time option to say you don't want Python at all, but I can't remember
if there was a load-as-needed option.
In any event, the current situation is what it is. What's feasible and
worth doing for the future?
* Hard
I see a bunch of eros here:
http://lists.llvm.org/pipermail/www-scripts/2019-November/thread.html
Is this possibly related to the Github/monorepo transition?
-- Jonas
On Thu, Nov 21, 2019 at 10:52 AM Adrian Prantl via lldb-dev
wrote:
>
> Hello Tanya,
>
> it looks like the cron job that is suppo
What kind of behavior did you expect?
I could be wrong, but I thought that previous versions of LLDB would use
LoadLibrary() instead of linking to the import library?
From: Pavel Labath
Sent: Wednesday, November 20, 2019 11:32 PM
To: Adrian McCarthy ; Leonard Mos
Hello Tanya,
it looks like the cron job that is supposed to be updating the LLDB website
isn't running or is otherwise blocked at the moment. You can see on
https://lldb.llvm.org that it says "Welcome to the LLDB version 8
documentation!". We also recently removed the "Why a New Debugger?" head
> In addition to being used for post-commit testing, having these CI
definitions in the
> main tree will make it easier for me (or anyone) to do pre-commit testing
for the
> release branch in a personal fork.
I find this part especially useful. I'm using these actions on a personal
branch to valid
