Update YASM to fix the command error#12324
Update YASM to fix the command error#12324JackBoosY wants to merge 6 commits intomicrosoft:masterfrom
Conversation
|
@voskrese @Neumann-A @timautry @Sibras Could you please test this PR? Thanks. |
|
I can't repro these regressions on my machine. |
|
and only test add slash |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
My log is: The pipeline log is: But I can build successful on my machine (both Visual Studio 2017 and 2019). |
|
cache azure subdir yasm version x84? subdir x64 and x86 |
|
@voskrese No, they are in downloads/tools/yasm/1.3.0.6. |
|
delete add ? |
|
@voskrese and I found the following code doesn't work: |
I experimented with this for myself, plus the definition of the version |
|
@BillyONeal Could you take a look? Thanks. |
|
test, delete
|
yasm old 2014 the possible error due to the lack of
|
I think this is a bug of yasm. I'll report it later. |
|
I have to wait for the official to fix this bug. |
|
Maybe we should just build a newer version of yasm ourself and use that? |
|
@Neumann-A Therefore, we have to add yasm as a port. |
|
@JackBoosY: Therefore, we cannot do it because we are not allowed to do so? Maybe the MS team should discuss again if vcpkg should support tools as ports or have a separate git for binary tools. I mean llvm/qmake etc. are already built by vcpkg, so why not the complete rest? |
|
@Neumann-A We need to discuss it. |
yasm perl and others pacman -S mingw-w64-x86_64-yasm pacman -S mingw-w64-x86_64-perl |
|
Temporary close this PR, will continue this work in the future. |
|
This issue will be fixed in #14003 instead. |
Using the new YASM binary seems to solve the path problem in the command line, so update it.
Fixes #12240 #12237.