MantisBT - CMake
View Issue Details
0014308CMakeCMakepublic2013-07-24 06:252016-06-10 14:31
ycollet 
Kitware Robot 
normalminoralways
closedmoved 
Intel 64 bitsWindows7
CMake 2.8.9 
 
0014308: NMake Makefiles do not mark phony targets such that NMake understands
I use Visual Studio 2008 with 64 bits compilation support.
Under Linux, I launch my tests via make test.
Under Windows, if I launch "nmake test", the tests are note started. I've got the following message:

e:\ycollet\RiskManager\build_tmp_64>nmake test

Microsoft (R) Program Maintenance Utility Version 9.00.21022.08
Copyright (C) Microsoft Corporation. Tous droits réservés.

'test' is up to date


If I edit Makefile and rename the 'test' rule into 'yc', nmake yc launch the tests.
I suspect a problem with nmake.
No tags attached.
Issue History
2013-07-24 06:25ycolletNew Issue
2013-07-24 07:12ycolletNote Added: 0033584
2013-07-24 07:18ycolletNote Added: 0033585
2013-07-24 13:50Brad KingNote Added: 0033594
2013-07-24 13:50Brad KingStatusnew => backlog
2013-07-24 13:50Brad KingSummaryWith "NMake Makefiles" generators under visual studio 2008 nmake test doesn't work => NMake Makefiles do not mark phony targets such that NMake understands
2016-06-10 14:29Kitware RobotNote Added: 0042324
2016-06-10 14:29Kitware RobotStatusbacklog => resolved
2016-06-10 14:29Kitware RobotResolutionopen => moved
2016-06-10 14:29Kitware RobotAssigned To => Kitware Robot
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0033584)
ycollet   
2013-07-24 07:12   
It's the same when compiling using the 32 bits DOS console.
nmake test doesn't work.
(0033585)
ycollet   
2013-07-24 07:18   
I found the reason on a blog:

http://dingevoninteresse.de/wpblog/?p=259 [^]

I've got a test directory which seems to interfere with the nmake test rule.
(0033594)
Brad King   
2013-07-24 13:50   
NMake does not understand CMake's ".PHONY" mark:

 http://stackoverflow.com/questions/4509033/nmake-phony-analogue [^]
(0042324)
Kitware Robot   
2016-06-10 14:29   
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.