Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Visual Studio project: link to libogg, libvorbis and libvorbisfile
Required for pull request #3851 that was recently merged.
- Loading branch information
Showing
1 changed file
with
5 additions
and
5 deletions.
There are no files selected for viewing
This file contains 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
86c2833
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know the static libraries are what we are discussing in aquileia/external, but I note that we are including libogg, libvorbis, and libvorbisfile in the Wesnoth Windows releases. Should we consider using the DLLs instead?
86c2833
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't follow your logic.
86c2833
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here we are linking to the static libraries. Yet we already have libogg-0.dll, libvorbis-0.dll, and libvorbisfile-3.dll included in the release package. Doesn't this mean we're duplicating the ogg/vorbis code? (Static libraries + DLLs)
86c2833
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmmm.... good point. How do we only use the dlls?
86c2833
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the xiph.org packages I noticed there are static and dynamic VC projects. I used the the dynamic project to build the DLL and LIB files, then configured my VC project to link to, for example, libvorbis.lib (instead of libvorbis_static.dll).
I apologise, I probably should have included all this as part of my pull request in the first place.
86c2833
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, right. I saw those. The relevant DLLs are from SDL_Mixer, so we should note that should we someday no longer need Mixer we'll have to keep those DLLs.
86c2833
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It should be obvious that they need to be kept. We have the music in Ogg Vorbis format, and it stands to reason that we need libogg and libvorbis to play them. (Currently the situation simply is that we use them through SDL_Mixer rather than directly.)
Aside, we should replace the copies of libogg and libvorbis shipped with SDL_Mixer with our own. It's not a good idea to mix the headers and the .lib files from one version with the DLL of another version.