[build] Fix d3d10 and ddraw dependencies#41
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
While I was building Sarek, I spotted a small derp in the D7VK DDraw meson script: it shouldn't link with
d3d9.dllifddraw.dllis compiled independently of the D3D9 module, but rather list the native d3d9 library as a dependency.Going from there, I also spotted a similar derp (fixed upstream, probably ages ago) related to
d3d10core.dlland addressed that as well.Now there's two less steps to account for during compilation, and a couple of warnings are also gone.
Since I was looking over everything, I also ported back the upstream release script. It has some nice new flags for building only 32/64-bit, which are useful during testing.