(0034927)
Nils Gladitz (developer)
2014-01-11 09:50

The visual studio generators do not require the visual studio developer command prompt environments.
They are only required when using the "NMake Makefiles" or similar generators.

I tried the "NMake Makefiles" and the "Visual Studio 11" generators with both 32 and 64 bit and seem to be getting identical "config.h"s.

They all contain e.g. "#define HAVE_CMATH 1".

Is that entry missing for you as well or are you missing other specific entries?

(0034929)
Brad King (manager)
2014-01-13 09:23

To use the VS IDE with x64 tools use the "Visual Studio 11 Win64" generator in cmake-gui or at any prompt. To use NMake at the x64 tools command prompt use the "NMake Makefiles" generator.

(0035231)
Brad King (manager)
2014-03-03 09:31

I suspect that this issue is also the cause of the problems in 0014642.

What happens if you run CMake from a generic prompt with no VS environment configured to create a fresh build tree from a fresh source tree?

(0035249)
Brad King (manager)
2014-03-04 15:43

Re 0014693:0035231: Let's start with the simplest case rather than involving plplot or wxWidgets. Create a fresh source tree containing just the file:

>type CMakeLists.txt
cmake_minimum_required(VERSION 2.8)
project(Issue14693 C)

foreach(v
    CMAKE_CL_64
    CMAKE_C_COMPILER
  )
  message(STATUS "${v}=${${v}}")
endforeach()

Then try building as follows:

>mkdir b
>cd b
>cmake .. -G "Visual Studio 11 Win64"

What is the output?

(0035251)
philrosenberg (reporter)
2014-03-04 18:31

Hi Brad
So when I test this simple example all seems as it should. Output below

-- The C compiler identification is MSVC 17.0.61030.0
-- Check for working C compiler using: Visual Studio 11 2012 Win64
-- Check for working C compiler using: Visual Studio 11 2012 Win64 -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- CMAKE_CL_64=1
-- CMAKE_C_COMPILER=C:/Program Files (x86)/Microsoft Visual Studio 11.0/VC/bin/x
86_amd64/cl.exe
-- Configuring done
-- Generating done
-- Build files have been written to: D:/usr/local/src/cmake test/b

(0035313)
Brad King (manager)
2014-03-05 13:35

Re 0014693:0035251: Since the simple case works then it may be something plplot is doing. I think they have some custom platform information files to support extra languages and such. Please ask them for help running CMake on their project.

(0038697)
Robert Maynard (manager)
2015-05-04 09:05

Closing resolved issues that have not been updated in more than 4 months.

Issue History
Date Modified	Username	Field	Change
2014-01-11 07:51	philrosenberg	New Issue
2014-01-11 09:50	Nils Gladitz	Note Added: 0034927
2014-01-13 09:23	Brad King	Note Added: 0034929
2014-03-03 08:57	Brad King	Relationship added	related to 0014642
2014-03-03 09:31	Brad King	Note Added: 0035231
2014-03-04 15:43	Brad King	Note Added: 0035249
2014-03-04 18:31	philrosenberg	Note Added: 0035251
2014-03-05 13:35	Brad King	Note Added: 0035313
2014-12-15 09:09	Brad King	Status	new => resolved
2014-12-15 09:09	Brad King	Resolution	open => suspended
2015-05-04 09:05	Robert Maynard	Note Added: 0038697
2015-05-04 09:05	Robert Maynard	Status	resolved => closed

Notes
(0034927) Nils Gladitz (developer) 2014-01-11 09:50	The visual studio generators do not require the visual studio developer command prompt environments. They are only required when using the "NMake Makefiles" or similar generators. I tried the "NMake Makefiles" and the "Visual Studio 11" generators with both 32 and 64 bit and seem to be getting identical "config.h"s. They all contain e.g. "#define HAVE_CMATH 1". Is that entry missing for you as well or are you missing other specific entries?

(0034929) Brad King (manager) 2014-01-13 09:23	To use the VS IDE with x64 tools use the "Visual Studio 11 Win64" generator in cmake-gui or at any prompt. To use NMake at the x64 tools command prompt use the "NMake Makefiles" generator.

(0035231) Brad King (manager) 2014-03-03 09:31	I suspect that this issue is also the cause of the problems in 0014642. What happens if you run CMake from a generic prompt with no VS environment configured to create a fresh build tree from a fresh source tree?

(0035249) Brad King (manager) 2014-03-04 15:43	Re 0014693:0035231: Let's start with the simplest case rather than involving plplot or wxWidgets. Create a fresh source tree containing just the file: >type CMakeLists.txt cmake_minimum_required(VERSION 2.8) project(Issue14693 C) foreach(v CMAKE_CL_64 CMAKE_C_COMPILER ) message(STATUS "${v}=${${v}}") endforeach() Then try building as follows: >mkdir b >cd b >cmake .. -G "Visual Studio 11 Win64" What is the output?

(0035251) philrosenberg (reporter) 2014-03-04 18:31	Hi Brad So when I test this simple example all seems as it should. Output below -- The C compiler identification is MSVC 17.0.61030.0 -- Check for working C compiler using: Visual Studio 11 2012 Win64 -- Check for working C compiler using: Visual Studio 11 2012 Win64 -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- CMAKE_CL_64=1 -- CMAKE_C_COMPILER=C:/Program Files (x86)/Microsoft Visual Studio 11.0/VC/bin/x 86_amd64/cl.exe -- Configuring done -- Generating done -- Build files have been written to: D:/usr/local/src/cmake test/b

(0035313) Brad King (manager) 2014-03-05 13:35	Re 0014693:0035251: Since the simple case works then it may be something plplot is doing. I think they have some custom platform information files to support extra languages and such. Please ask them for help running CMake on their project.

(0038697) Robert Maynard (manager) 2015-05-04 09:05	Closing resolved issues that have not been updated in more than 4 months.