Re: [CMake] Correct way to build for 64 bit?
Stephane Rouleau (Consultant) wrote: That's not what I wanted to read of course. :) Has there been any thoughts given to adding support for this? When building through a vcproj you can cross-compile win32/x64 on 32 and 64 bits Windows, provided the proper compiler tools have been installed. Anyway, it's not the end of the world. Thanks for the quick reply, Bill. Sounds interesting I did not know that was possible. Do you have instructions on how to set something like that up? -Bill ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
RE: [CMake] Correct way to build for 64 bit?
That's not what I wanted to read of course. :) Has there been any thoughts given to adding support for this? When building through a vcproj you can cross-compile win32/x64 on 32 and 64 bits Windows, provided the proper compiler tools have been installed. Anyway, it's not the end of the world. Thanks for the quick reply, Bill. Stephane -Original Message- From: Bill Hoffman [mailto:[EMAIL PROTECTED] Sent: February 23, 2007 5:02 PM To: Stephane Rouleau (Consultant) Cc: cmake@cmake.org Subject: Re: [CMake] Correct way to build for 64 bit? Stephane Rouleau (Consultant) wrote: > [snip] > 2. For the windows cl, a try compile is done to figure out which cl > you are using. For the IDE, there is a separate generator for the 64 > bit tool because you have to use a different tool. So, you either run > vcvars64.bat then cmake for nmake, or you pick the 64 bit IDE build. > [...] > > I've just started playing with cmake, downloaded the source to go > along with the documentation, so I may be reading this wrong... > > It looks like with the current incarnation you cannot generate a > single .vcproj with two platforms (one for Win32, one for x64), and so > we'd have to run cmake twice and specify different output directories > for the two solution files. Am I reading this correctly? > That is correct, you have to run CMake twice, once for 32 bit and once for 64 bit, just use different output directories. -Bill ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Re: Trouble with libraries on MacOS X
Thomas Christian Chust wrote: Brandon J. Van Every wrote: Thomas Christian Chust wrote: I consider this seriously buggy behaviour. First of all I don't like it that the build system magically wipes out one of the library targets I ordered it to create. [...] This can be prevented by setting the CLEAN_DIRECT_OUTPUT property to 1." [...] Thanks, that's good to know. Probably the reason that I didn't find it in the documentation is that the CMake documentation installed with the CMake binary package for MacOS X does not contain any reference to this setting... This capability was added relatively recently, maybe in CMake 2.4.5. What version of CMake are you using? Cheers, Brandon Van Every ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Correct way to build for 64 bit?
Stephane Rouleau (Consultant) wrote: [snip] 2. For the windows cl, a try compile is done to figure out which cl you are using. For the IDE, there is a separate generator for the 64 bit tool because you have to use a different tool. So, you either run vcvars64.bat then cmake for nmake, or you pick the 64 bit IDE build. [...] I've just started playing with cmake, downloaded the source to go along with the documentation, so I may be reading this wrong... It looks like with the current incarnation you cannot generate a single .vcproj with two platforms (one for Win32, one for x64), and so we'd have to run cmake twice and specify different output directories for the two solution files. Am I reading this correctly? That is correct, you have to run CMake twice, once for 32 bit and once for 64 bit, just use different output directories. -Bill ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Re: Trouble with libraries on MacOS X
Brandon J. Van Every wrote: > Thomas Christian Chust wrote: > >> I consider this seriously buggy behaviour. First of all I don't like it >> that the build system magically wipes out one of the library targets I >> ordered it to create. > > [...] This can be prevented by setting the > CLEAN_DIRECT_OUTPUT property to 1." [...] Thanks, that's good to know. Probably the reason that I didn't find it in the documentation is that the CMake documentation installed with the CMake binary package for MacOS X does not contain any reference to this setting... cu, Thomas Chust ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
[CMake] Correct way to build for 64 bit?
[snip] 2. For the windows cl, a try compile is done to figure out which cl you are using. For the IDE, there is a separate generator for the 64 bit tool because you have to use a different tool. So, you either run vcvars64.bat then cmake for nmake, or you pick the 64 bit IDE build. [...] I've just started playing with cmake, downloaded the source to go along with the documentation, so I may be reading this wrong... It looks like with the current incarnation you cannot generate a single .vcproj with two platforms (one for Win32, one for x64), and so we'd have to run cmake twice and specify different output directories for the two solution files. Am I reading this correctly? Thank you, Stephane Rouleau ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
[CMake] Re: Trouble with libraries on MacOS X
Thomas Christian Chust wrote: I consider this seriously buggy behaviour. First of all I don't like it that the build system magically wipes out one of the library targets I ordered it to create. See SET_TARGET_PROPERTIES in the docs. "When a library is built CMake by default generates code to remove any existing library using all possible names. This is needed to support libraries that switch between STATIC and SHARED by a user option. However when using OUTPUT_NAME to build a static and shared library of the same name using different logical target names the two targets will remove each other's files. This can be prevented by setting the CLEAN_DIRECT_OUTPUT property to 1." I haven't tried this approach in Chicken. I solved the problem by putting the static libs in their own subdirectory. The design is not ideal. Ideally, CMake would make collision decisions based on the full name of the library, including prefixes, postfixes, and suffixes. On Unixy toolchains it is standard drill that suffixes distinguish shared vs. static libraries. On MSVC unfortunately it is not; everything ends in .lib. Personally I think it would be acceptable to have the MSVC generator die with an error message. The MSVC buildmaster can either disambiguate with the various *_POSTFIX options, name the libraries differently, or put libraries in separate directories. Cheers, Brandon Van Every ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
RE: [CMake] Progress report
It can go above 100% if you are using an old version of CMake (2.4.3 maybe or older) or if you have multiple makes running at the same time. (not make -j that is OK, but "make foo" in one shell while you do "make bar" in another shell where foo and bar are in the same Makefile) This can also happen I believe if you invoke a make in the same tree as part of a custom command within a current make. They are pretty odd cases. Ken Ken Martin PhD Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 518 371 3971 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Felix Winkelmann Sent: Friday, February 23, 2007 8:07 AM To: cmake@cmake.org Subject: [CMake] Progress report Hi! Just a tiny, trvial thing... I have the problem that the progress report shows me something long 120% when finished. The relevant CMakeLists.txt is here: http://galinha.ucpel.tche.br/chicken/CMakeLists.txt This behaviour appears to exist on all platforms that I know of (Linux, Windows, OS X), and I'm not sure how to get more details. How does the progress report mechanism work? cheers, felix ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
[CMake] Trouble with libraries on MacOS X
Hello, I'm using CMake 2.4.6 on a PowerPC iBook running MacOS X 10.4.8 and I found some issues with building both shared and static libraries and with linking to static libraries using CMake. I have attached a very simple example project to this e-mail that can be used to demonstrate the problems. If you have a look at the CMakeLists.txt in the example, you can see that it states that both a shared and a static library should be built from the same sources plus an executable should be built and linked against the static version of the library. Now if you create a build directory for the project using CMake and run make in it, both libraries and the executable are built -- but somewhere in the build process the dynamic library is deleted again, so it is gone from the output directory when the build finishes! Of course, as the dynamic library has disappeared, the executable that is produced is linked against the remaining static library, which is also what the CMakeLists.txt specifies. But now, in order to keep both libraries try the following in the build directory: make clean make lib_shared mkdir tmp mv liblib.dylib tmp make lib_static mv tmp/liblib.dylib . And then build the executable that is specified to link against the static version of the library: make use If you check the resulting executable with otool -L, you will see that it is now dynamically linked against liblib.dylib instead of statically against liblib.a. I consider this seriously buggy behaviour. First of all I don't like it that the build system magically wipes out one of the library targets I ordered it to create. But the more serious problem is the linkage issue: As CMake tries to be clever and converts any absolute path to a library passed to TARGET_LINK_LIBRARIES into a combination of -L and -l flags for the linker, it is completely impossible to link against a static library on MacOS X if a dynamic library of the same name exists anywhere on the library search path! The MacOS X linker always prefers dynamic libraries over static ones if it can find them anywhere. Is there any portable workaround for this problem? Of course I can always manually handle the linker flags correctly, but that's tedious and exactly the type of thing I want to avoid by using CMake. cu, Thomas Chust cmakebug.tar.gz Description: Unix tar archive ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
[CMake] Progress report
Hi! Just a tiny, trvial thing... I have the problem that the progress report shows me something long 120% when finished. The relevant CMakeLists.txt is here: http://galinha.ucpel.tche.br/chicken/CMakeLists.txt This behaviour appears to exist on all platforms that I know of (Linux, Windows, OS X), and I'm not sure how to get more details. How does the progress report mechanism work? cheers, felix ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
[CMake] building from CVS fails on Linux
Hi! I get: % configure - CMake 2.5-20070219, Copyright (c) 2006 Kitware, Inc., Insight Consortium C compiler on this system is: cc C++ compiler on this system is: g++ Makefile processor on this system is: gmake g++ is GNU compiler g++ has STL in std:: namespace g++ has ANSI streams g++ has streams in std:: namespace g++ has sstream g++ has operator!=(string, char*) g++ has stl iterator_traits g++ has standard template allocator g++ has allocator<>::rebind<> g++ does not have non-standard allocator<>::max_size argument g++ has stl containers supporting allocator objects g++ has header cstddef g++ requires template friends to use <> g++ supports member templates g++ has standard template specialization syntax g++ has argument dependent lookup g++ has struct stat with st_mtim member g++ has ANSI for scoping - g++ -I/home/fwinkel/stuff/CMake/Source -I/home/fwinkel/stuff/CMake/Bootstrap.cmk -c /home/fwinkel/stuff/CMake/Source/cmLocalGenerator.cxx -o cmLocalGenerator.o /home/fwinkel/stuff/CMake/Source/cmLocalGenerator.cxx: In member function ` std::string cmLocalGenerator::EscapeForShell(const char*, bool, bool)': /home/fwinkel/stuff/CMake/Source/cmLocalGenerator.cxx:2377: error: ` cmsysSystem_Shell_Flag_WatcomWMake' undeclared (first use this function) /home/fwinkel/stuff/CMake/Source/cmLocalGenerator.cxx:2377: error: (Each undeclared identifier is reported only once for each function it appears in.) gmake: *** [cmLocalGenerator.o] Error 1 - Error when bootstrapping CMake: Problem while running gmake - Log of errors: /home/fwinkel/stuff/CMake/Bootstrap.cmk/cmake_bootstrap.log - % cheers, felix ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Problem using cmake with mingw
Claudiu-Daniel wrote: I'm trying to compile OIS with cmake I've managed to do this with a VS 2005 solution generated by cmake and it works fine but when i try to do it with a mingw makefile I get this error D:\ScatteredLands\Project\trunk\buildgcc>mingw32-make Scanning dependencies of target ois [ 0%] Building CXX object external/ois-1.0RC1/CMakeFiles/ois.dir/src/OISEffect.obj [ 1%] Building CXX object external/ois-1.0RC1/CMakeFiles/ois.dir/src/OISForceFeedback.obj mingw32-make[2]: *** No rule to make target `C:/Program Files/Microsoft DirectX SDK \(February 2007\)/Include/dinput.h', needed by `external/ois-1.0RC1/CMak eFiles/ois.dir/src/OISInputManager.obj'. Stop. mingw32-make[1]: *** [external/ois- 1.0RC1/CMakeFiles/ois.dir/all] Error 2 mingw32-make: *** [all] Error 2 I have just put a fix into CVS CMake that allows for () in paths to be correctly handled. You will have to try CVS CMake. -Bill ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
[CMake] Problem using cmake with mingw
I'm trying to compile OIS with cmake
I've managed to do this with a VS 2005 solution generated by cmake and it
works fine but when i try to do it with a mingw makefile I get this error
D:\ScatteredLands\Project\trunk\buildgcc>mingw32-make
Scanning dependencies of target ois
[ 0%] Building CXX object external/ois-1.0RC1
/CMakeFiles/ois.dir/src/OISEffect.obj
[ 1%] Building CXX object external/ois-1.0RC1
/CMakeFiles/ois.dir/src/OISForceFeedback.obj
mingw32-make[2]: *** No rule to make target `C:/Program Files/Microsoft
DirectX SDK \(February 2007\)/Include/dinput.h', needed by `external/ois-
1.0RC1/CMak
eFiles/ois.dir/src/OISInputManager.obj'. Stop.
mingw32-make[1]: *** [external/ois- 1.0RC1/CMakeFiles/ois.dir/all] Error 2
mingw32-make: *** [all] Error 2
Here is the code From CMakeLists.txt
#builds the ois library
set(SRC_FILES"src/OISEffect.cpp"
"src/OISForceFeedback.cpp"
"src/OISInputManager.cpp"
"src/OISJoyStick.cpp"
"src/OISKeyboard.cpp"
"src/OISObject.cpp")
set(INCLUDE_DIR "${TSLRPG_SOURCE_DIR}/external/ois- 1.0RC1/includes")
set(LIBS "")
set(LINK_DIRS "")
if(WIN32)
SET(CMAKE_FIND_LIBRARY_PREFIXES "")
SET(CMAKE_FIND_LIBRARY_SUFFIXES ".lib")
find_package(DirectX)
set(INCLUDE_DIR ${INCLUDE_DIR}
"${TSLRPG_SOURCE_DIR}/external/ois-1.0RC1/includes/win32"
${DirectX_INCLUDE_DIR})
set(LIBS ${LIBS} dxguid dinput8)
set(LINK_DIRS ${LINK_DIRS} ${DirectX_LIB_DIR})
set(SRC_FILES ${SRC_FILES}
"src/win32/Win32ForceFeedBack.cpp"
"src/win32/Win32InputManager.cpp"
"src/win32/Win32JoyStick.cpp"
"src/win32/Win32KeyBoard.cpp"
"src/win32/Win32Mouse.cpp")
endif(WIN32)
include_directories( ${INCLUDE_DIR} )
link_directories( ${LINK_DIRS} )
add_library( ois ${SRC_FILES} )
target_link_libraries( ois ${LIBS})
Here is the code from FindDirectX.cmake
# - Test for DirectX
# Once loaded this will define
# DirectX_FOUND- system has DirectX
# DirectX_INCLUDE_DIR - include directory for DirectX
# DirectX_LIB_DIR - lib directory for DirectX
set(DirectX_FOUND "NO")
if(WIN32)
find_path(DirectX_INCLUDE_DIR "dinput.h"
"C:/Program Files/Microsoft DirectX SDK (October 2006)/Include"
"C:/Program Files/Microsoft DirectX SDK (February 2007)/Include"
"C:/Program Files/Microsoft Visual Studio .NET
2003/Vc7/PlatformSDK/Include"
"C:/Program Files/Microsoft DirectX SDK (February 2006)/Include"
"C:/Program Files/Microsoft DirectX 9.0 SDK (June 2005)/Include"
"C:/DXSDK/Include")
find_path(DirectX_LIB_DIR "dinput8.lib"
"C:/Program Files/Microsoft DirectX SDK (October 2006)/Lib/x86"
"C:/Program Files/Microsoft DirectX SDK (February 2007)/Lib/x86"
"C:/Program Files/Microsoft Visual Studio .NET
2003/Vc7/PlatformSDK/Lib"
"C:/Program Files/Microsoft DirectX SDK (February 2006)/Lib"
"C:/Program Files/Microsoft DirectX 9.0 SDK (June 2005)/Lib"
"C:/DXSDK/Lib")
if(DirectX_INCLUDE_DIR AND DirectX_LIB_DIR)
set(DirectX_FOUND "YES")
endif(DirectX_INCLUDE_DIR AND DirectX_LIB_DIR)
else(WIN32)
endif(WIN32)
if (DirectX_FOUND)
if (NOT DirectX_FIND_QUIETLY)
message(STATUS "Found DirectX: ${DirectX_LIBRARIES}")
endif (NOT DirectX_FIND_QUIETLY)
else (DirectX_FOUND)
if (DirectX_FIND_REQUIRED)
message(FATAL_ERROR "Could not find DirectX")
endif (DirectX_FIND_REQUIRED)
endif (DirectX_FOUND)
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
[CMake] Problem using cmake with mingw
I'm trying to compile OIS with cmake
I've managed to do this with a VS 2005 solution generated by cmake and it
works fine but when i try to do it with a mingw makefile I get this error
D:\ScatteredLands\Project\trunk\buildgcc>mingw32-make
Scanning dependencies of target ois
[ 0%] Building CXX object external/ois-1.0RC1
/CMakeFiles/ois.dir/src/OISEffect.obj
[ 1%] Building CXX object external/ois-1.0RC1
/CMakeFiles/ois.dir/src/OISForceFeedback.obj
mingw32-make[2]: *** No rule to make target `C:/Program Files/Microsoft
DirectX SDK \(February 2007\)/Include/dinput.h', needed by `external/ois-
1.0RC1/CMak
eFiles/ois.dir/src/OISInputManager.obj'. Stop.
mingw32-make[1]: *** [external/ois- 1.0RC1/CMakeFiles/ois.dir/all] Error 2
mingw32-make: *** [all] Error 2
Here is the code From CMakeLists.txt
#builds the ois library
set(SRC_FILES"src/OISEffect.cpp"
"src/OISForceFeedback.cpp"
"src/OISInputManager.cpp"
"src/OISJoyStick.cpp"
"src/OISKeyboard.cpp"
"src/OISObject.cpp")
set(INCLUDE_DIR "${TSLRPG_SOURCE_DIR}/external/ois- 1.0RC1/includes")
set(LIBS "")
set(LINK_DIRS "")
if(WIN32)
SET(CMAKE_FIND_LIBRARY_PREFIXES "")
SET(CMAKE_FIND_LIBRARY_SUFFIXES ".lib")
find_package(DirectX)
set(INCLUDE_DIR ${INCLUDE_DIR}
"${TSLRPG_SOURCE_DIR}/external/ois-1.0RC1/includes/win32"
${DirectX_INCLUDE_DIR})
set(LIBS ${LIBS} dxguid dinput8)
set(LINK_DIRS ${LINK_DIRS} ${DirectX_LIB_DIR})
set(SRC_FILES ${SRC_FILES}
"src/win32/Win32ForceFeedBack.cpp"
"src/win32/Win32InputManager.cpp"
"src/win32/Win32JoyStick.cpp"
"src/win32/Win32KeyBoard.cpp"
"src/win32/Win32Mouse.cpp")
endif(WIN32)
include_directories( ${INCLUDE_DIR} )
link_directories( ${LINK_DIRS} )
add_library( ois ${SRC_FILES} )
target_link_libraries( ois ${LIBS})
Here is the code from FindDirectX.cmake
# - Test for DirectX
# Once loaded this will define
# DirectX_FOUND- system has DirectX
# DirectX_INCLUDE_DIR - include directory for DirectX
# DirectX_LIB_DIR - lib directory for DirectX
set(DirectX_FOUND "NO")
if(WIN32)
find_path(DirectX_INCLUDE_DIR "dinput.h"
"C:/Program Files/Microsoft DirectX SDK (October 2006)/Include"
"C:/Program Files/Microsoft DirectX SDK (February 2007)/Include"
"C:/Program Files/Microsoft Visual Studio .NET
2003/Vc7/PlatformSDK/Include"
"C:/Program Files/Microsoft DirectX SDK (February 2006)/Include"
"C:/Program Files/Microsoft DirectX 9.0 SDK (June 2005)/Include"
"C:/DXSDK/Include")
find_path(DirectX_LIB_DIR "dinput8.lib"
"C:/Program Files/Microsoft DirectX SDK (October 2006)/Lib/x86"
"C:/Program Files/Microsoft DirectX SDK (February 2007)/Lib/x86"
"C:/Program Files/Microsoft Visual Studio .NET
2003/Vc7/PlatformSDK/Lib"
"C:/Program Files/Microsoft DirectX SDK (February 2006)/Lib"
"C:/Program Files/Microsoft DirectX 9.0 SDK (June 2005)/Lib"
"C:/DXSDK/Lib")
if(DirectX_INCLUDE_DIR AND DirectX_LIB_DIR)
set(DirectX_FOUND "YES")
endif(DirectX_INCLUDE_DIR AND DirectX_LIB_DIR)
else(WIN32)
endif(WIN32)
if (DirectX_FOUND)
if (NOT DirectX_FIND_QUIETLY)
message(STATUS "Found DirectX: ${DirectX_LIBRARIES}")
endif (NOT DirectX_FIND_QUIETLY)
else (DirectX_FOUND)
if (DirectX_FIND_REQUIRED)
message(FATAL_ERROR "Could not find DirectX")
endif (DirectX_FIND_REQUIRED)
endif (DirectX_FOUND)
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
[CMake] Fwd: Problem using cmake with mingw
-- Forwarded message --
From: Claudiu-Daniel <[EMAIL PROTECTED]>
Date: Feb 23, 2007 10:41 AM
Subject: Problem using cmake with mingw
To: cmake@cmake.org
I'm trying to compile OIS with cmake
I've managed to do this with a VS 2005 solution generated by cmake and it
works fine but when i try to do it with a mingw makefile I get this error
D:\ScatteredLands\Project\trunk\buildgcc>mingw32-make
Scanning dependencies of target ois
[ 0%] Building CXX object external/ois-1.0RC1
/CMakeFiles/ois.dir/src/OISEffect.obj
[ 1%] Building CXX object external/ois-1.0RC1
/CMakeFiles/ois.dir/src/OISForceFeedback.obj
mingw32-make[2]: *** No rule to make target `C:/Program Files/Microsoft
DirectX SDK \(February 2007\)/Include/dinput.h', needed by `external/ois-
1.0RC1/CMak
eFiles/ois.dir/src/OISInputManager.obj'. Stop.
mingw32-make[1]: *** [external/ois- 1.0RC1/CMakeFiles/ois.dir/all] Error 2
mingw32-make: *** [all] Error 2
Here is the code From CMakeLists.txt
#builds the ois library
set(SRC_FILES"src/OISEffect.cpp"
"src/OISForceFeedback.cpp"
"src/OISInputManager.cpp"
"src/OISJoyStick.cpp"
"src/OISKeyboard.cpp"
"src/OISObject.cpp")
set(INCLUDE_DIR "${TSLRPG_SOURCE_DIR}/external/ois- 1.0RC1/includes")
set(LIBS "")
set(LINK_DIRS "")
if(WIN32)
SET(CMAKE_FIND_LIBRARY_PREFIXES "")
SET(CMAKE_FIND_LIBRARY_SUFFIXES ".lib")
find_package(DirectX)
set(INCLUDE_DIR ${INCLUDE_DIR}
"${TSLRPG_SOURCE_DIR}/external/ois-1.0RC1/includes/win32"
${DirectX_INCLUDE_DIR})
set(LIBS ${LIBS} dxguid dinput8)
set(LINK_DIRS ${LINK_DIRS} ${DirectX_LIB_DIR})
set(SRC_FILES ${SRC_FILES}
"src/win32/Win32ForceFeedBack.cpp"
"src/win32/Win32InputManager.cpp"
"src/win32/Win32JoyStick.cpp"
"src/win32/Win32KeyBoard.cpp"
"src/win32/Win32Mouse.cpp")
endif(WIN32)
include_directories( ${INCLUDE_DIR} )
link_directories( ${LINK_DIRS} )
add_library( ois ${SRC_FILES} )
target_link_libraries( ois ${LIBS})
Here is the code from FindDirectX.cmake
# - Test for DirectX
# Once loaded this will define
# DirectX_FOUND- system has DirectX
# DirectX_INCLUDE_DIR - include directory for DirectX
# DirectX_LIB_DIR - lib directory for DirectX
set(DirectX_FOUND "NO")
if(WIN32)
find_path(DirectX_INCLUDE_DIR "dinput.h"
"C:/Program Files/Microsoft DirectX SDK (October 2006)/Include"
"C:/Program Files/Microsoft DirectX SDK (February 2007)/Include"
"C:/Program Files/Microsoft Visual Studio .NET
2003/Vc7/PlatformSDK/Include"
"C:/Program Files/Microsoft DirectX SDK (February 2006)/Include"
"C:/Program Files/Microsoft DirectX 9.0 SDK (June 2005)/Include"
"C:/DXSDK/Include")
find_path(DirectX_LIB_DIR "dinput8.lib"
"C:/Program Files/Microsoft DirectX SDK (October 2006)/Lib/x86"
"C:/Program Files/Microsoft DirectX SDK (February 2007)/Lib/x86"
"C:/Program Files/Microsoft Visual Studio .NET
2003/Vc7/PlatformSDK/Lib"
"C:/Program Files/Microsoft DirectX SDK (February 2006)/Lib"
"C:/Program Files/Microsoft DirectX 9.0 SDK (June 2005)/Lib"
"C:/DXSDK/Lib")
if(DirectX_INCLUDE_DIR AND DirectX_LIB_DIR)
set(DirectX_FOUND "YES")
endif(DirectX_INCLUDE_DIR AND DirectX_LIB_DIR)
else(WIN32)
endif(WIN32)
if (DirectX_FOUND)
if (NOT DirectX_FIND_QUIETLY)
message(STATUS "Found DirectX: ${DirectX_LIBRARIES}")
endif (NOT DirectX_FIND_QUIETLY)
else (DirectX_FOUND)
if (DirectX_FIND_REQUIRED)
message(FATAL_ERROR "Could not find DirectX")
endif (DirectX_FIND_REQUIRED)
endif (DirectX_FOUND)
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
