Changes between Initial Version and Version 1 of Community/Tasks/CMake

Show
Ignore:
Timestamp:
07/13/07 15:02:53 (7 years ago)
Author:
martin (IP: 81.178.2.19)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Community/Tasks/CMake

    v1 v1  
     1= CMake = 
     2[[TracNav(TracNav/SupportTOC)]] 
     3 
     4CMake documentation pages can build found at [wiki:Build/CMake CMake] which are also linked to from the main [wiki:Support] index page. 
     5 
     6Below are some old links/discussion on the CMake build project that has been integrated into the core !OpenSceneGraph and !OpenThreads SVN. 
     7 
     8---- 
     9 
     10== Position papers written by members of the community == 
     11 * Luigi Calori's [attachment:osgcmake.zip paper] on his CMake/OSG work submitted to the Highland Gathering 2006. Document in is zipped .odp file (Open Document Presentation). 
     12 
     13== Mac OS X Specific Notes: == 
     14There are still some standing issues on OS X. There are several things that we need on OS X: 
     15 * Framework detection support (a framework is a fancy packaged dynamic library) 
     16 * Framework creation support (to build osg frameworks instead of just .dylibs) 
     17 * Universal Binary support (either through Xcode, Makefiles, or both) 
     18 * install_name support (sort of like rpath on Linux) 
     19 
     20We have been in discussion with the CMake authors and they seem to be willing to help us. Per our request, they have already implemented framework detection support. There seems to be at least a workaround for install_name. There seems to be confidence that Framework creation support should not be too hard to implement and we are just trying to finalize the CMake API for it. Universal Binary support is more of a pain because CMake wasn't built around the idea of cross-compiling. However the best path is to leverage Apple's changes to gcc and Xcode and accomplish this task. Since OSG has a fairly unified code base without a lot of processor specific stuff, we are hopeful that CMake will implement the set of features we need to do this. 
     21 
     22With that being said, CMake is still closest to meeting these OS X objectives than any other cross-platform build systems (for many of these issues aren't even on those projects' radar). 
     23