Skip to content
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

Add VSYASM download link in FFmpeg/SMP/readme.txt #51

Closed
wants to merge 1 commit into from

Conversation

BensonLaur
Copy link

Context

YASM is required by projects under Visual Studio Solution ffmpeg_deps.sln including libass.vcxproj, libgmp.vcxproj, libgnutls.vcxproj, libhogweed.vcxproj, libnettle.vcxproj, libvpx.vcxproj and libxvidcore.vcxproj.

It would be better to add download link of VSYASM

YASM is required by project under Visual Studio Solution ffmpeg_deps.sln including libass.vcxproj, libgmp.vcxproj,  libgnutls.vcxproj, libhogweed.vcxproj, libnettle.vcxproj, libvpx.vcxproj and libxvidcore.vcxproj.
@Sibras
Copy link
Member

Sibras commented Oct 15, 2019

To build ffmpeg only NASM can be used so i wanted to be clear on that.

As for YASM dependency that can change based on what the dependencies require. So i dont explicitly state it in ffmpeg as whenever a dependency changes then ffmpeg has to be changed as well. Which is why in the readme i refer users to the readme of the dependencies to see what they need with:

Some of these dependency projects have additional requirements to those listed here. See the corresponding readme for each of the projects for further details.

Although i did fix a typo in the readme that you spotted.

@BensonLaur
Copy link
Author

Ok, thanks for explanation

@BensonLaur BensonLaur closed this Oct 15, 2019
@BensonLaur
Copy link
Author

BensonLaur commented Oct 15, 2019

Just, as a beginner, I was so confused when those dependencies requiring YASM failed to be loaded

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants