labath added subscribers: aleksandr.urakov, amccarth, ted, labath. labath added a comment.
Yeah, I'd still like to avoid having multiple paths for configuring python, as one of them is bound to end up broken sooner or later. However, given that there's already talk about bumping the minimum cmake version, maybe we could do an lldb-specific bump first? Though I am generally against aggressive version bumps, this python+windows situation is sufficiently messy that I think the bump may be worth it. Given that this code is python3 specific and other platforms still support python2, maybe we can make this bump windows-specific at first, and then extend it to other platforms once we officially stop supporting python2 ? [+ other windows stakeholders: @amccarth, @ted, @aleksandr.urakov ] ================ Comment at: lldb/cmake/modules/LLDBConfig.cmake:225 + if(CMAKE_VERSION VERSION_GREATER_EQUAL 3.13 AND CMAKE_SYSTEM_NAME STREQUAL Windows) + find_package(Python3 COMPONENTS Interpreter Development REQUIRED) + if(Python3_VERSION VERSION_LESS 3.5) ---------------- What if I use a single-config generator and build a release configuration. Is the "development" thingy still required? Repository: rLLDB LLDB CHANGES SINCE LAST ACTION https://reviews.llvm.org/D69535/new/ https://reviews.llvm.org/D69535 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
