View Issue Details Jump to Notes ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0012540CMakeCMakepublic2011-10-26 04:472016-06-10 14:31
ReporterMartin Apel 
Assigned ToKitware Robot 
PrioritynormalSeveritymajorReproducibilityalways
StatusclosedResolutionmoved 
PlatformIntelOSWindowsOS VersionWindows 7
Product VersionCMake 2.8.6 
Target VersionFixed in Version 
Summary0012540: Error configuring project using Intel Fortran with Visual Studio generator
DescriptionWe have a project setup, which uses C, C++ and Fortran. Additionally we have defined custom build types with compile flags for these build types.
Up to 2.8.6-rc2 this project could be configured using the Visual Studio 9 2008 generator without problems. Since 2.8.6-rc3 (and also the final 2.8.6 release) the configuration step generates errors related to our custom build types:

-- Check for working Fortran compiler using: Visual Studio 9 2008
CMake Error: Error required internal CMake variable not set, cmake may be not be
 built correctly.
Missing variable is:
CMAKE_Fortran_FLAGS_NOOPT
CMake Error: Error required internal CMake variable not set, cmake may be not be
 built correctly.
Missing variable is:
CMAKE_EXE_LINKER_FLAGS_NOOPT
CMake Error: Error required internal CMake variable not set, cmake may be not be
 built correctly.
Missing variable is:
CMAKE_Fortran_FLAGS_DEBUGWARN
CMake Error: Error required internal CMake variable not set, cmake may be not be
 built correctly.
Missing variable is:
CMAKE_EXE_LINKER_FLAGS_DEBUGWARN

The suffixes DEBUGWARN and NOOPT stem from our custom build types.
Unfortunately I have not succeeded in creating a small sample project, which reproduces the problem.

Performing the same configuration with other generators such as NMake on Windows or Make on Linux succeeds without problems.
Additional InformationI have attached to trace files generated by cmake-2.8.6-rc2 and cmake-2.8.6-rc3
when calling cmake -G "Visual Studio 9 2008" --trace <source dir>
TagsNo tags attached.
Attached Filesgz file icon traces.tar.gz [^] (218,385 bytes) 2011-10-26 04:47

 Relationships

  Notes
(0030318)
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.
(0041923)
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.

 Issue History
Date Modified Username Field Change
2011-10-26 04:47 Martin Apel New Issue
2011-10-26 04:47 Martin Apel File Added: traces.tar.gz
2012-08-11 11:38 David Cole Status new => backlog
2012-08-11 11:38 David Cole Note Added: 0030318
2016-06-10 14:28 Kitware Robot Note Added: 0041923
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


Copyright © 2000 - 2018 MantisBT Team