[Python-Dev] Evaluated cmake as an autoconf replacement (original) (raw)
Neil Hodgson nyamatongwe at gmail.com
Fri Apr 10 03:49:04 CEST 2009
- Previous message: [Python-Dev] Evaluated cmake as an autoconf replacement
- Next message: [Python-Dev] Evaluated cmake as an autoconf replacement
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
cmake does not produce relative paths in its generated make and project files. There is an option CMAKE_USE_RELATIVE_PATHS which appears to do this but the documentation says:
"""This option does not work for more complicated projects, and relative paths are used when possible. In general, it is not possible to move CMake generated makefiles to a different location regardless of the value of this variable."""
This means that generated Visual Studio project files will not work for other people unless a particular absolute build location is specified for everyone which will not suit most. Each person that wants to build Python will have to run cmake before starting Visual Studio thus increasing the prerequisites.
Neil
- Previous message: [Python-Dev] Evaluated cmake as an autoconf replacement
- Next message: [Python-Dev] Evaluated cmake as an autoconf replacement
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]