| View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0012436 | CMake | CMake | public | 2011-08-31 10:46 | 2016-06-10 14:31 | ||||
| Reporter | Andrew Wiggin | ||||||||
| Assigned To | Kitware Robot | ||||||||
| Priority | normal | Severity | minor | Reproducibility | always | ||||
| Status | closed | Resolution | moved | ||||||
| Platform | PC | OS | Windows | OS Version | 7 (64-bit) | ||||
| Product Version | CMake 2.8.4 | ||||||||
| Target Version | Fixed in Version | ||||||||
| Summary | 0012436: Default project generation is inconsistent between cmake-gui and cmake (command line) | ||||||||
| Description | I start either cmake-gui or cmake from a command prompt that has is setup for compilation using VS10 64-bit compilers. cmake-gui correctly detects the build environment and generates projects that are targeted at 64-bit, but cmake generates projects that are targeted at 32-bit. | ||||||||
| Steps To Reproduce | on 64-bit machine with vs10 installed, from a 64-bit command prompt: Type the following to setup a 64-bit environment (changing based on where vs10 is installed of course) "c:\program files (x86)\microsoft visual studio 10.0\vc\vcvarsall" x64 And then use cmake & cmake-gui to generate build files for your project, without changing any defaults. Load the projects into VS10 and compare the target platforms. | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files | |||||||||
| Relationships | |
| Relationships |
| Notes | |
|
(0027311) Rolf Eike Beer (developer) 2011-08-31 10:58 |
I assume you did cmake path/to/source Which will tell cmake to build using the default generator. If you have some older version of MSVC installed in parallel this could as well be such one, e.g. I often saw MSVC6 projects being generated. The CMake command line interface isn't really designed to do such "fancy autodetection". If you want a MSVC10 x64 project then tell it: cmake -G "Visual Studio 10 Win64" path/to/source (or however this generator is called) |
|
(0030300) David Cole (manager) 2012-08-11 11:38 |
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. |
|
(0041899) Kitware Robot (administrator) 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. |
| Notes |
| Issue History | |||
| Date Modified | Username | Field | Change |
| 2011-08-31 10:46 | Andrew Wiggin | New Issue | |
| 2011-08-31 10:58 | Rolf Eike Beer | Note Added: 0027311 | |
| 2012-08-11 11:38 | David Cole | Status | new => backlog |
| 2012-08-11 11:38 | David Cole | Note Added: 0030300 | |
| 2016-06-10 14:28 | Kitware Robot | Note Added: 0041899 | |
| 2016-06-10 14:28 | Kitware Robot | Status | backlog => resolved |
| 2016-06-10 14:28 | Kitware Robot | Resolution | open => moved |
| 2016-06-10 14:28 | Kitware Robot | Assigned To | => Kitware Robot |
| 2016-06-10 14:31 | Kitware Robot | Status | resolved => closed |
| Issue History |
| Copyright © 2000 - 2018 MantisBT Team |