View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0001701 | CMake | public | 2005-03-22 12:46 | 2005-04-05 12:17 | |||||
Reporter | Hans Johnson | ||||||||
Assigned To | Bill Hoffman | ||||||||
Priority | low | Severity | minor | Reproducibility | always | ||||
Status | closed | Resolution | no change required | ||||||
Platform | OS | OS Version | |||||||
Product Version | |||||||||
Target Version | Fixed in Version | ||||||||
Summary | 0001701: Starting ccmake makes too many assumptions | ||||||||
Description | As soon as ccmake is started on unix, values are filled out in the cache. Example: trying to use distcc as the compiler for a project. Distcc is a wrapper around gcc compiler that allows distrubuted compilation across a network. input: ccmake -DCMAKE_C_COMPILER=distcc -DCMAKE_CC_COMPILER=distcc result: this fail in the initial testing. work around: ccmake -DCMAKE_C_COMPILER=gcc -DCMAKE_CC_COMPILER=g++ ccmake -DCMAKE_C_COMPILER=distcc -DCMAKE_CC_COMPILER=distcc result: everything works. | ||||||||
Tags | No tags attached. | ||||||||
Attached Files | |||||||||
Relationships | |
Relationships |
Notes | |
(0002251) Brad King (manager) 2005-03-29 10:27 |
What do you suggest should be the behavior in your example? |
(0002252) Hans Johnson (reporter) 2005-03-29 10:55 |
I would suggest the the ccmake respects the command line for configuration. It appears that the command line arguments are not processed until after the gcc compiler is already found and some of the cache values are filled in. |
(0002279) Bill Hoffman (manager) 2005-04-05 12:17 |
CMAKE_C_COMPILER and CMAKE_CXX_COMPILER are the correct variables to use. It seems to work for me with both 2.0.5 and the current cvs. |
Notes |
Issue History | |||
Date Modified | Username | Field | Change |
Issue History |
Copyright © 2000 - 2018 MantisBT Team |