MantisBT - CMake
View Issue Details
0012246CMakeCMakepublic2011-06-04 06:352016-06-10 14:31
Thomas Laguzzi 
Kitware Robot 
normalminoralways
closedmoved 
Win32WindowsWindows XP
CMake 2.8.4 
 
0012246: CMake NMake generator /machine defect
I have found a way to reproduce 0010695 where building with Nmake causes link failure

"No argument passed to /machine:"

The problem comes when the user does wrong the first NMake configuration
1- Open cmake-gui without compiler environment variables (i.e. open from Start->Run...)
2- Configure a project with NMake . You will get errors complaining about not finding the compiler
3- Close cmake-gui
4- Run cmake-gui from a VS command prompt
5- Configure (without deleting cache). This time the compiler is found.
6- Build -> get the error
It seems that the /machine: flag is not re-set in successive configurations even when the first failed.

Not an important bug, but can block beginners
No tags attached.
Issue History
2011-06-04 06:35Thomas LaguzziNew Issue
2011-06-18 09:40David ColeNote Added: 0026908
2012-08-11 11:38David ColeStatusnew => backlog
2012-08-11 11:38David ColeNote Added: 0030271
2016-06-10 14:28Kitware RobotNote Added: 0041846
2016-06-10 14:28Kitware RobotStatusbacklog => resolved
2016-06-10 14:28Kitware RobotResolutionopen => moved
2016-06-10 14:28Kitware RobotAssigned To => Kitware Robot
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0026908)
David Cole   
2011-06-18 09:40   
Just as an FYI for anybody doing an investigation here...... There was a problem one day with our bug tracker, where we had to restore the database from a previous day. And in the process we lost the original bug with id 12246.

Thanks to our process, though, teh Googles Interwebz has preserved the information for us. See this mailing list archive entry for the original bug 0012246:

  http://public.kitware.com/pipermail/cmake-developers/2011-June/001665.html [^]
(0030271)
David Cole   
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.
(0041846)
Kitware Robot   
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.