On Tue, Apr 15, 2008 at 11:47 AM, Jean-Sébastien Guay < [EMAIL PROTECTED]> wrote:
> Hi JP, > > >> where are you getting these CMake packages from? On the CMake site it > >> says latest version is 2.4.8? > > > > Interesting, I thought the fact they had started making 2.7 snapshots > > meant that at least the 2.6 stable release was out... But it appears it > > isn't. > > > > See http://www.cmake.org/files/vCVS/ > > > > Perhaps that means we can put off supporting them till after the OSG 2.4 > > release? > > Just to make it clear, I agree, I was getting ahead of myself by getting > the CVS snapshot and assuming that CMake 2.6 was current. So we can > probably ignore what I said about the change in library directory > semantics in CMake for now, and only address it when CMake versions >= > 2.6 are officially released. The change in library directory semantics is fairly low-key. You can see an example of the differences below. The big difference is that DLLs will be placed in CMAKE_RUNTIME_OUTPUT_DIRECTORY. I'm not sure how this affects the PREFIX target property that CMake uses now for DLL placement. Someone would need to test this. I do know EXECUTABLE_OUTPUT_PATH and LIBRARY_OUTPUT_PATH are completely backwards compatible, merely deprecated in CMake 2.6. IF(CMAKE_MAJOR_VERSION EQUAL 2 AND CMAKE_MINOR_VERSION GREATER 4) SET(CMAKE_LIBRARY_OUTPUT_DIRECTORY ${PROJECT_BINARY_DIR}/lib CACHE STRING "Where libraries go" FORCE) SET(CMAKE_ARCHIVE_OUTPUT_DIRECTORY ${PROJECT_BINARY_DIR}/lib CACHE STRING "Where archives go" FORCE) SET(CMAKE_RUNTIME_OUTPUT_DIRECTORY ${PROJECT_BINARY_DIR}/bin CACHE STRING "Where binaries and .dll files go" FORCE) ELSE() SET(EXECUTABLE_OUTPUT_PATH ${PROJECT_BINARY_DIR}/bin CACHE STRING "Where binaries go" FORCE) SET(LIBRARY_OUTPUT_PATH ${PROJECT_BINARY_DIR}/lib CACHE STRING "Where libraries go" FORCE) ENDIF() -- Philip Lowman
_______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
