Remove trailing whitespace from most CMake and C/C++ code

Our Git commit hooks disallow modification or addition of lines with
trailing whitespace.  Wipe out all remnants of trailing whitespace
everywhere except third-party code.

Run the following shell code:

git ls-files -z -- \
 bootstrap doxygen.config '*.readme' \
 '*.c' '*.cmake' '*.cpp' '*.cxx' \
 '*.el' '*.f' '*.f90' '*.h' '*.in' '*.in.l' '*.java' \
 '*.mm' '*.pike' '*.py' '*.txt' '*.vim' |
egrep -z -v '^(Utilities/cm|Source/(kwsys|CursesDialog/form)/)' |
egrep -z -v '^(Modules/CPack\..*\.in)' |
xargs -0 sed -i 's/ \+$//'

1 files changed, 15 insertions, 15 deletions

diff --git a/Modules/FindOpenAL.cmake b/Modules/FindOpenAL.cmake
index cb3ce48..fdac455 100644
--- a/Modules/FindOpenAL.cmake
+++ b/Modules/FindOpenAL.cmake
@@ -1,7 +1,7 @@
 # Locate OpenAL
 # This module defines
 # OPENAL_LIBRARY
-# OPENAL_FOUND, if false, do not try to link to OpenAL 
+# 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
@@ -25,31 +25,31 @@
 
 # This makes the presumption that you are include al.h like
 # #include "al.h"
-# and not 
+# 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 
+# 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 
+#
+# 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 
+# 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 
+# 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 
+#
+# 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 
+# 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. 
+# framework.
 # Per my request, CMake should search for frameworks first in
 # the following order:
 # ~/Library/Frameworks/OpenAL.framework/Headers
@@ -57,7 +57,7 @@
 # /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 
+# 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.
 
@@ -75,7 +75,7 @@ FIND_PATH(OPENAL_INCLUDE_DIR al.h
   [HKEY_LOCAL_MACHINE\\SOFTWARE\\Creative\ Labs\\OpenAL\ 1.1\ Software\ Development\ Kit\\1.00.0000;InstallDir]
 )
 
-FIND_LIBRARY(OPENAL_LIBRARY 
+FIND_LIBRARY(OPENAL_LIBRARY
   NAMES OpenAL al openal OpenAL32
   HINTS
   $ENV{OPENALDIR}