You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
FindVorbis.cmake is producing the following warning.
CMake Warning (dev) at C:/Program Files/Microsoft Visual Studio/2022/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/CMake/share/cmake-3.22/Modules/FindPackageHandleStandardArgs.cmake:438 (message):The package name passed to `find_package_handle_standard_args` (VORBIS)
does not match the name of the calling package (Vorbis). This can lead to
problems in calling code that expects `find_package` result variables
(e.g., `_FOUND`) to follow a certain pattern.
Which is coming from a mismatch in the FindVorbis.cmake at Line 25 find_package_handle_standard_args(VORBIS DEFAULT_MSG VORBIS_LIBRARIES VORBIS_INCLUDE_DIR OGG_INCLUDE_DIR)
This is by no means critical, and isn't causing any issues as far as I can tell since it isn't really exposed to end users. Though it is still passing the warning to the end user in certain cases which should be avoided where possible, and it's a simple fix (Changing find_package_handle_standard_args's target to Vorbis).
Your environment
Windows 11
SFML 2.5.1 and CMake 3.22
Steps to reproduce
Using the following CMake build script you can reproduce the warning.
Subject of the issue
FindVorbis.cmake is producing the following warning.
Which is coming from a mismatch in the FindVorbis.cmake at Line 25
find_package_handle_standard_args(VORBIS DEFAULT_MSG VORBIS_LIBRARIES VORBIS_INCLUDE_DIR OGG_INCLUDE_DIR)
This is by no means critical, and isn't causing any issues as far as I can tell since it isn't really exposed to end users. Though it is still passing the warning to the end user in certain cases which should be avoided where possible, and it's a simple fix (Changing
find_package_handle_standard_args
's target toVorbis
).Your environment
Steps to reproduce
Using the following CMake build script you can reproduce the warning.
The text was updated successfully, but these errors were encountered: