View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0000786 | CMake | public | 2004-04-22 20:01 | 2004-04-28 13:56 | |||||
Reporter | Andrew Maclean | ||||||||
Assigned To | Bill Hoffman | ||||||||
Priority | low | Severity | minor | Reproducibility | always | ||||
Status | closed | Resolution | fixed | ||||||
Platform | OS | OS Version | |||||||
Product Version | |||||||||
Target Version | Fixed in Version | ||||||||
Summary | 0000786: Incorrect Python execuatable selected. | ||||||||
Description | Using VC7.1 Assumes that the windows version of Python and the Cygwin version of Python are installed. In this case, when searching for python.exe, CMake always selects the cygwin version even though it correctly picks out the windows version for the Libs. So you have to manually change the path. Can this be automated so that when the windows version of Python libs are used the windows version of Python.exe is selected? | ||||||||
Tags | No tags attached. | ||||||||
Attached Files | |||||||||
Relationships | |
Relationships |
Notes | |
(0000954) Bill Hoffman (manager) 2004-04-23 08:30 |
Not much we can do about this. CMake looks in your PATH for finding executables. If you do not have cygwin in your path it will not happen. But cmake will run the executable that you would run from that shell. |
(0000996) Bill Hoffman (manager) 2004-04-28 13:56 |
This was a bug in ITK and CableSwig cmakelist files. They looked for python22 before just plain python. If there is a plain python in the path, it should be picked. cygwin has a python22.exe but windows only has a python.exe so the cygwin one was prefred. I have checked in a fix into the ITK tree. |
Notes |
Issue History | |||
Date Modified | Username | Field | Change |
Issue History |
Copyright © 2000 - 2018 MantisBT Team |