{"push_id":811556829,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"4de808f4438d458f38a3090d63fbe868842b87dd","before":"0eda1c90b3a92764f1f4bcbce33dc5105ace546f","commits":[{"sha":"4de808f4438d458f38a3090d63fbe868842b87dd","author":{"email":"ccac2bfac288d9a152e61e5cc31e0235e83ee810@gmail.com","name":"Bruce Mitchener"},"message":"Add a Post-Build Event on Windows to copy the correct custom Python DLL to the LLDB binaries dir\n\nSummary:\nAfter a developer builds LLDB from source on Windows (assuming they've built it with Python support enabled), they may be somewhat flustered when it fails to launch with a cryptic error.\n\n{F890625}\n\nThis happens because Windows can't find python27.dll (or python27_d.dll in case LLDB was built in debug mode). Many developers may have previously installed a release build of Python 2.7 and will not notice anything is amiss when they run a release build of LLDB because Windows will load the python27.dll from one of the system directories or `PATH` (rather than the one that the LLDB build instructions tell them to build). The issue tends to be more pronounced with debug builds of LLDB, since fewer developers probably have python27_d.dll sitting in one of the Windows system directories.\n\nTo ensure Windows loads the correct custom built Python DLL when launching LLDB I've added a post-build event that copies the relevant DLL (based on the LLDB build configuration) from `PYTHON_HOME` to the directory in which the LLDB executable is generated.\n\nPatch by Vadim Macagon. Thanks!\n\nReviewers: brucem, zturner\n\nSubscribers: lldb-commits\n\nDifferential Revision: http://reviews.llvm.org/D13237","distinct":true,"url":"https://api.github.com/repos/llvm-project/llvm-project/commits/4de808f4438d458f38a3090d63fbe868842b87dd"}]}