MantisBT - CMake
View Issue Details
0012577CMakeCMakepublic2011-11-14 09:232016-06-10 14:31
Mathias Gaunard 
Kitware Robot 
normalminoralways
closedmoved 
x86_64Linux3.0.0-12-generic
CMake-2-8 
 
0012577: CMAKE_SYSTEM_XXX variables should not be modified when cross-compiling
The file Modules/Platform/UnixPaths.cmake always appends /usr/local and other paths to CMAKE_SYSTEM_PREFIX_PATH when on a Unix-like system, and likewise for include and library paths.

This prevents setting up some cross-compiling scenarios which cannot be set-up using the CMAKE_FIND_ROOT_PATH mechanism.

I think all CMAKE_SYSTEM_XXX variables defined in a Toolchain file should have priority and not be modified.
Putting those variables in the cache does not work either, the variables can still be modified.
No tags attached.
Issue History
2011-11-14 09:23Mathias GaunardNew Issue
2012-08-11 21:09David ColeStatusnew => backlog
2012-08-11 21:09David ColeNote Added: 0030328
2016-06-10 14:28Kitware RobotNote Added: 0041932
2016-06-10 14:28Kitware RobotStatusbacklog => resolved
2016-06-10 14:28Kitware RobotResolutionopen => moved
2016-06-10 14:28Kitware RobotAssigned To => Kitware Robot
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0030328)
David Cole   
2012-08-11 21:09   
Sending old, never assigned issues to the backlog.

(The age of the bug, plus the fact that it's never been assigned to anyone means that nobody is actively working on it...)

If an issue you care about is sent to the backlog when you feel it should have been addressed in a different manner, please bring it up on the CMake mailing list for discussion. Sign up for the mailing list here, if you're not already on it: http://www.cmake.org/mailman/listinfo/cmake [^]

It's easy to re-activate a bug here if you can find a CMake developer who has the bandwidth to take it on, and ferry a fix through to our 'next' branch for dashboard testing.
(0041932)
Kitware Robot   
2016-06-10 14:28   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page.