On Thu, 2019-10-10 at 23:11 +0000, Ted Woodward wrote:
> Starting in r372835 (Fix installing Python modules on systems using 
> /usr/lib), the finish_swig and installation steps using multi-configuration 
> generators (like Visual Studio or XCode) are broken.
> 
> The problem is the symlink and install steps look for liblldb and 
> site-packages the wrong directories.
> 
> For the symlink, I get this output:
>          Making symlink from ..\..\..\bin\liblldb.dll to 
> i:\obj\lib\site-packages\lldb\_lldb.pyd
> ...
>          WindowsError: [Error 2] The system cannot find the file specified: 
> '..\\..\\..\\bin\\liblldb.dll'
> 
> Because the cwd is I:\obj\Lib\site-packages\lldb, not the correct 
> I:\obj\Release\Lib\site-packages\lldb. liblldb.dll is in i:\obj\Release\bin, 
> not i:\obj\bin. Also, the link itself should be in i:\obj\Release\lib, not 
> i:\obj\lib.
> 
> The problem is the cmake code went from using LLVM_LIBRARY_OUTPUT_INTDIR to 
> CMAKE_BINARY_DIR. CMAKE_BINARY_DIR is not complete for multi-configuration 
> generators - you need to specify the configuration as well.
> 
[...]
> Michal, please try this and see if it still works for the issue you fixed in 
> r372835.

Actually, I see that Haibo has already addressed this 2 days ago.  Could
you test if his solution (r374250) works for you?

-- 
Best regards,
Michał Górny

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Reply via email to