New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix separate make and install execution error issue. #8540
Conversation
@Christsnatcher @spindensity @oracleoftroy @timautry |
I've tested it. It works perfectly. Thanks. |
To be honest, I'm a bit surprised it worked, but it worked for me as well. I don't know what vcpkg's policy is for making sure vcpkg still works if installed in paths with spaces, but I suspect the change on line 55 of |
@oracleoftroy Well, I think this is due to the simultaneous use of |
Hmm, I see. I wish I understood cmake and vcpkg internals better. I got stuck at this part. It just surprised me that a few quotes added and removed was all it took. :) |
Thank you @JackBoosY, working fine here either. |
@JackBoosY |
@Neumann-A: The removal of these particular quotes apparently isn't necessary, I just tried and x264 building worked flawlessly with the quotes in place. |
@JackBoosY I took a look at the quotes on line 55 this morning and I can confirm what @Christsnatcher says. I added quotes around just the make executable, changing line 55 to:
I had no issue installing x264 with this change. |
@JackBoosY: Got this error in WSL with this PR merged into my libpq PR:
|
Solved it with |
@Neumann-A I don't understand the difference between command and parameter splitting between windows and linux, but it is successful with your workaround. Good work! |
Thank you @JackBoosY - does the job on both VS2017 and VS2019 latest builds. I appreciate the hard work you put in on this. Have a wonderful week. |
Working perfectly now, a huge "Thank you" to everyone involved in fixing this issue! |
The install command has not been executed, it looks like it was caused by the separation of make and install.
Related: #8473.