mirror of
https://github.com/reactos/CMake.git
synced 2024-11-29 06:20:23 +00:00
c4275592a8
The FindPackageHandleStandardArgs module was originally created outside of CMake. It was added for CMake 2.6.0 by commite118a627(add a macro FIND_PACKAGE_HANDLE_STANDARD_ARGS..., 2007-07-18). However, it also proliferated into a number of other projects that at the time required only CMake 2.4 and thus could not depend on CMake to provide the module. CMake's own find modules started using the module in commitb5f656e0(use the new FIND_PACKAGE_HANDLE_STANDARD_ARGS in some of the FindXXX modules..., 2007-07-18). Then commitd358cf5c(add 2nd, more powerful mode to find_package_handle_standard_args, 2010-07-29) added a new feature to the interface of the module that was fully optional and backward compatible with all existing users of the module. Later commit5f183caa(FindZLIB: use the FPHSA version mode, 2010-08-04) and others shortly thereafter started using the new interface in CMake's own find modules. This change was also backward compatible because it was only an implementation detail within each module. Unforutnately these changes introduced a problem for projects that still have an old copy of FindPackageHandleStandardArgs in CMAKE_MODULE_PATH. When any such project uses one of CMake's builtin find modules the line include(FindPackageHandleStandardArgs) loads the copy from the project which does not have the new interface! Then the including find module tries to use the new interface with the old module and fails. Whether this breakage can be considered a backward incompatible change in CMake is debatable. The situation is analagous to copying a standard library header from one version of a compiler into a project and then observing problems when the next version of the compiler reports errors in its other headers that depend on its new version of the original header. Nevertheless it is a change to CMake that causes problems for projects that worked with previous versions. This problem was discovered during the 2.8.3 release candidate cycle. It is an instance of a more general problem with projects that provide their own versions of CMake modules when other CMake modules depend on them. At the time we resolved this instance of the problem with commitb0118402(Use absolute path to FindPackageHandleStandardArgs.cmake everywhere, 2010-09-28) for the 2.8.3 release. In order to address the more general problem we introduced policy CMP0017 in commitdb44848f(Prefer files from CMAKE_ROOT when including from CMAKE_ROOT, 2010-11-17). That change was followed by commitce28737c(Remove usage of CMAKE_CURRENT_LIST_DIR now that we have CMP0017, 2010-12-20) which reverted the original workaround in favor of using the policy. However, existing project releases do not set the policy behavior to NEW and therefore still exhibit the problem. We introduced in commita364daf1(Allow users to specify defaults for unset policies, 2011-01-03) an option for users to build existing projects by adding -DCMAKE_POLICY_DEFAULT_CMP0017=NEW to the command line. Unfortunately this solution still does not allow such projects to build out of the box, and there is no good way to suggest the use of the new option. The only remaining solution to keep existing projects that exhibit this problem building is to restore the change originally made in commitb0118402(Use absolute path to FindPackageHandleStandardArgs.cmake everywhere, 2010-09-28). This also avoids policy CMP0017 warnings for this particular instance of the problem the policy addresses.
104 lines
3.9 KiB
CMake
104 lines
3.9 KiB
CMake
# Locate OpenAL
|
|
# This module defines
|
|
# OPENAL_LIBRARY
|
|
# OPENAL_FOUND, if false, do not try to link to OpenAL
|
|
# OPENAL_INCLUDE_DIR, where to find the headers
|
|
#
|
|
# $OPENALDIR is an environment variable that would
|
|
# correspond to the ./configure --prefix=$OPENALDIR
|
|
# used in building OpenAL.
|
|
#
|
|
# Created by Eric Wing. This was influenced by the FindSDL.cmake module.
|
|
|
|
#=============================================================================
|
|
# Copyright 2005-2009 Kitware, Inc.
|
|
#
|
|
# Distributed under the OSI-approved BSD License (the "License");
|
|
# see accompanying file Copyright.txt for details.
|
|
#
|
|
# This software is distributed WITHOUT ANY WARRANTY; without even the
|
|
# implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
|
# See the License for more information.
|
|
#=============================================================================
|
|
# (To distribute this file outside of CMake, substitute the full
|
|
# License text for the above reference.)
|
|
|
|
# This makes the presumption that you are include al.h like
|
|
# #include "al.h"
|
|
# and not
|
|
# #include <AL/al.h>
|
|
# The reason for this is that the latter is not entirely portable.
|
|
# Windows/Creative Labs does not by default put their headers in AL/ and
|
|
# OS X uses the convention <OpenAL/al.h>.
|
|
#
|
|
# For Windows, Creative Labs seems to have added a registry key for their
|
|
# OpenAL 1.1 installer. I have added that key to the list of search paths,
|
|
# however, the key looks like it could be a little fragile depending on
|
|
# if they decide to change the 1.00.0000 number for bug fix releases.
|
|
# Also, they seem to have laid down groundwork for multiple library platforms
|
|
# which puts the library in an extra subdirectory. Currently there is only
|
|
# Win32 and I have hardcoded that here. This may need to be adjusted as
|
|
# platforms are introduced.
|
|
# The OpenAL 1.0 installer doesn't seem to have a useful key I can use.
|
|
# I do not know if the Nvidia OpenAL SDK has a registry key.
|
|
#
|
|
# For OS X, remember that OpenAL was added by Apple in 10.4 (Tiger).
|
|
# To support the framework, I originally wrote special framework detection
|
|
# code in this module which I have now removed with CMake's introduction
|
|
# of native support for frameworks.
|
|
# In addition, OpenAL is open source, and it is possible to compile on Panther.
|
|
# Furthermore, due to bugs in the initial OpenAL release, and the
|
|
# transition to OpenAL 1.1, it is common to need to override the built-in
|
|
# framework.
|
|
# Per my request, CMake should search for frameworks first in
|
|
# the following order:
|
|
# ~/Library/Frameworks/OpenAL.framework/Headers
|
|
# /Library/Frameworks/OpenAL.framework/Headers
|
|
# /System/Library/Frameworks/OpenAL.framework/Headers
|
|
#
|
|
# On OS X, this will prefer the Framework version (if found) over others.
|
|
# People will have to manually change the cache values of
|
|
# OPENAL_LIBRARY to override this selection or set the CMake environment
|
|
# CMAKE_INCLUDE_PATH to modify the search paths.
|
|
|
|
FIND_PATH(OPENAL_INCLUDE_DIR al.h
|
|
HINTS
|
|
$ENV{OPENALDIR}
|
|
PATH_SUFFIXES include/AL include/OpenAL include
|
|
PATHS
|
|
~/Library/Frameworks
|
|
/Library/Frameworks
|
|
/usr/local
|
|
/usr
|
|
/sw # Fink
|
|
/opt/local # DarwinPorts
|
|
/opt/csw # Blastwave
|
|
/opt
|
|
[HKEY_LOCAL_MACHINE\\SOFTWARE\\Creative\ Labs\\OpenAL\ 1.1\ Software\ Development\ Kit\\1.00.0000;InstallDir]
|
|
)
|
|
|
|
FIND_LIBRARY(OPENAL_LIBRARY
|
|
NAMES OpenAL al openal OpenAL32
|
|
HINTS
|
|
$ENV{OPENALDIR}
|
|
PATH_SUFFIXES lib64 lib libs64 libs libs/Win32 libs/Win64
|
|
PATHS
|
|
~/Library/Frameworks
|
|
/Library/Frameworks
|
|
/usr/local
|
|
/usr
|
|
/sw
|
|
/opt/local
|
|
/opt/csw
|
|
/opt
|
|
[HKEY_LOCAL_MACHINE\\SOFTWARE\\Creative\ Labs\\OpenAL\ 1.1\ Software\ Development\ Kit\\1.00.0000;InstallDir]
|
|
)
|
|
|
|
|
|
# handle the QUIETLY and REQUIRED arguments and set OPENAL_FOUND to TRUE if
|
|
# all listed variables are TRUE
|
|
INCLUDE(${CMAKE_CURRENT_LIST_DIR}/FindPackageHandleStandardArgs.cmake)
|
|
FIND_PACKAGE_HANDLE_STANDARD_ARGS(OpenAL DEFAULT_MSG OPENAL_LIBRARY OPENAL_INCLUDE_DIR)
|
|
|
|
MARK_AS_ADVANCED(OPENAL_LIBRARY OPENAL_INCLUDE_DIR)
|