dzhidzhoev wrote:
Closed in favor of https://github.com/llvm/llvm-project/pull/96654
https://github.com/llvm/llvm-project/pull/93887
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/dzhidzhoev closed
https://github.com/llvm/llvm-project/pull/93887
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
labath wrote:
Agreed. The reason code is looking like it does is because at some point in
(now, pretty distant) past it was possible to `cd` into the test directory,
type `make` and get the test binary out. Among other problems, this has caused
duplicate code for determining various
JDevlieghere wrote:
> Would it be possible to pass this automatically from the python process?
> Basically set `OS` to the value of `lldbplatformutil.getPlatform()` ? We
> could keep the existing exception for Android, although I don't think that
> anyone tests Android these days (your PRs
labath wrote:
Would it be possible to pass this automatically from the python process?
Basically set `OS` to the value of `lldbplatformutil.getPlatform()` ? We could
keep the existing exception for Android, although I don't think that anyone
tests Android these days (your PRs sort of
