Notes
(0035426) Brad King (manager) 2014-03-18 08:45	One approach that may help you work around this for now is to use an ITK install tree instead of a build tree if you are not already. That will have significantly fewer include directories.

(0035506) Yew Kurabayashi　 (reporter) 2014-03-25 11:35 edited on: 2014-03-25 11:43	Hi, Brad. Thank you for your reply! Your advice really helps me. In accordance with your suggestion, I installed ITK, and in CMake GUI, I set ITK_DIR to the directory in which ITKConfig.cmake is held and generated a solution. As you say, the number of include paths decreased significantly, but yet there were still too many paths in AM_MOC_INCLUDES, then moc failed again. So, I moved the source and the build tree of ParaView near the root directory so that the set of include paths becomes short on the whole. (I needed several days for that because I moved and rebuilt OpenCV and ITK besides ParaView.) Thanks to Brad, using install tree of ITK, and moving ParaView tree near the root, moc ran finally (but still too many paths in there). (In addition, there is still a problem with respect to Qt but it is another problem.) Finally, I have two requests for you all. 1. The utility class for Qt image inter-conversion in ITK and VTK like pqCoreUtilities in ParaView. Please implement and release it. It must help us. 2. Putting ParaViewConfig.cmake in the install tree of ParaView (like ITK). If it is possible and it makes the set of include paths be short, Qt 5 will be easy to use with ParaView together with other libraries. At present, ParaView is restricted to use with Qt 5 by the problem of this issue. Anyway, I appreciate Brad again and all the member of Kitware.

(0035522) Brad King (manager) 2014-03-26 08:58	Re 0014811:0035506: I'm glad you found workarounds. Please send the two feature requests to the respective projects as their developers do not necessarily read the CMake issue tracker. Can anyone more familiar with Qt, moc, and CMake's AUTOMOC features tell us whether this is a limitation of CMake or moc?

(0035523) Stephen Kelly (developer) 2014-03-26 09:08	The original report seems to say it's a limitation of moc (or of Windows command line limits?). The actual error was not posted, so I'm just guessing. Yew, please investigate where the limitation is and where the problem is introduced. Using at @-file for moc invocations might work, if that is confirmed as the limiting factor.

(0035535) Yew Kurabayashi　 (reporter) 2014-03-27 03:16 edited on: 2014-03-27 03:21	Stephen, I agree with you that it might be a limitation of moc or Windows command. But I don't know which is indeed. The reason why I posted this problem to this project is that it might be rather a quick compromise that CMake and other libraries of Kitware accommodate themselves for the limitation of moc and Windows. Because Kitware tools are the side of generating the solution for MSVC while moc and Windows are the receivers of its result. Anyway, I have tried some investigates and I put some information below. 1. Outputs and options from MSVC My MSVC is Japanese version, so I try to make a literal translation for Japanese messages in [ ]. 1-1. [Total options] I copy the options obtained from following way into attached file "MSVCOptions.txt". Right click on the project in MSVC, [Configuration property] - C/C++ - [Command line] - [Total options]. And in [Additional options], " /bigobj" is there. 1-2. Massages from build error I'll post these messages to subsequent comments for good legibility. Please forgive me to post many times. 2. Acceptable size of AutomocInfo.cmake for build 26kB is acceptable, but 39kB is rejected. I guess 32kB seems to be the limit. Since they say the limit of the length for the command line of Windows is 8kB, it might be the one of createProcess() called in the project of MSVC. But I don't know what is done precisely in the build process of the project. 3. moc invocation from command line with many options. moc invocation with too many include paths brings the following error message. moc: Too many input files specified This message is different from the message from MSVC. I attached the file "mocOptions.txt" that is used in the invocation "moc @ mocOptions.txt". The file includes the options of include paths only. Since I am just one of the end user, I don't know what should I do for this problem, but I hope these things help you all. Brad, I'll send my requests to the respective projects. Thanks again.

(0035536) Yew Kurabayashi　 (reporter) 2014-03-27 03:17	Output in MSVC ------ Build started: Project: ZERO_CHECK, Configuration: Release x64 ------ ------ Build started: Project: MocTest.2.0, Configuration: Release x64 ------ Generating moc_MyImageViewer.cpp パラメーターが間違っています。 [The parameters are (or The parameter is) wrong.] AUTOMOC : error : process for S:/study/Programs/C++/ITK/MocTest/2.0/bld/appricot/MSVC2012/moc_MyImageViewer.cpp failed: パラメーターが間違っています。 [The parameters are (or The parameter is) wrong.] moc failed... C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(124,5): error MSB3073: The command "setlocal C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(124,5): error MSB3073: cd S:\study\Programs\C++\ITK\MocTest\2.0\bld\appricot\MSVC2012 C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(124,5): error MSB3073: if %errorlevel% neq 0 goto :cmEnd C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(124,5): error MSB3073: S: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(124,5): error MSB3073: if %errorlevel% neq 0 goto :cmEnd C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(124,5): error MSB3073: "C:\Program Files (x86)\yew\CMake\2.8\bin\cmake.exe" -E cmake_automoc S:/study/Programs/C++/ITK/MocTest/2.0/bld/appricot/MSVC2012/CMakeFiles/MocTest.2.0_automoc.dir/ Release C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(124,5): error MSB3073: if %errorlevel% neq 0 goto :cmEnd C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(124,5): error MSB3073: :cmEnd C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(124,5): error MSB3073: endlocal & call :cmErrorLevel %errorlevel% & goto :cmDone C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(124,5): error MSB3073: :cmErrorLevel C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(124,5): error MSB3073: exit /b %1 C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(124,5): error MSB3073: :cmDone C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(124,5): error MSB3073: if %errorlevel% neq 0 goto :VCEnd C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(124,5): error MSB3073: :VCEnd" exited with code 1. ------ Build started: Project: ALL_BUILD, Configuration: Release x64 ------ Build all projects ========== Build: 2 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

(0035537) Yew Kurabayashi　 (reporter) 2014-03-27 03:18	Error List in MSVC Error 1 error : process for S:/study/Programs/C++/ITK/MocTest/2.0/bld/appricot/MSVC2012/moc_MyImageViewer.cpp failed: S:\study\Programs\C++\ITK\MocTest\2.0\bld\appricot\MSVC2012\AUTOMOC MocTest.2.0 Error 2 error MSB3073: The command "setlocal cd S:\study\Programs\C++\ITK\MocTest\2.0\bld\appricot\MSVC2012 if %errorlevel% neq 0 goto :cmEnd S: if %errorlevel% neq 0 goto :cmEnd "C:\Program Files (x86)\yew\CMake\2.8\bin\cmake.exe" -E cmake_automoc S:/study/Programs/C++/ITK/MocTest/2.0/bld/appricot/MSVC2012/CMakeFiles/MocTest.2.0_automoc.dir/ Release if %errorlevel% neq 0 goto :cmEnd :cmEnd endlocal & call :cmErrorLevel %errorlevel% & goto :cmDone :cmErrorLevel exit /b %1 :cmDone if %errorlevel% neq 0 goto :VCEnd :VCEnd" exited with code 1. C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets 124 5 MocTest.2.0

(0035538) Stephen Kelly (developer) 2014-03-27 04:30	AUTOMOC does not seem to generate an @-file. What is generating mocOptions.txt? Did you inspect mocOptions.txt to see if there was a bug within it? One path with spaces is spread over multiple lines. Please investigate if that's the problem.

(0035539) Yew Kurabayashi　 (reporter) 2014-03-27 05:05 edited on: 2014-03-27 05:06	I created the mocOptions.txt. It seems to be my misunderstanding. I apologize you that it confuses Stephen. I don't know what @-file means. So I regarded it as @<file> option for moc.

(0035540) Stephen Kelly (developer) 2014-03-27 05:23	Yes, when I wrote '@-file', I meant '@<file> option for moc.' Do you have a way of copy+pasting the exact command line used by cmake to invoke moc? If you do, then please post that.

(0035541) Yew Kurabayashi　 (reporter) 2014-03-27 05:55	I don't know how CMake invoke moc in the build process. Because the moc invocation is hidden in the back of the build process in MSVC. Instead, I can send all CMake related files in the build tree. Do you need them?

(0035542) Stephen Kelly (developer) 2014-03-27 06:57	I doubt the answer is in the cmake related files. It is more likely in the generated buildsystem. I suggest you run MSVC in a verbose mode if possible to see the command invocation, or search the generated buildsystem files for the moc invocation with whatever searching tools you have available.

(0035545) Yew Kurabayashi　 (reporter) 2014-03-28 02:02 edited on: 2014-03-28 02:07	I found that the call, "C:\Program Files (x86)\yew\CMake\2.8\bin\cmake.exe" -E cmake_automoc S:/study/Programs/C++/ITK/MocTest/3.0/1.automocFailure/bld/CMakeFiles/MocTest.3.0.1.automocFailure_automoc.dir/ Debug seems to invocate moc. Please refer to the line 431 in the file, "MSVCOutput.automocFailure.verbosity.4.detailed.txt" in the directory, "1.automocFailure\bld" in the attached file, "sampleProject.1.automocFailure.zip". The same content exists in "MocTest.3.0.1.automocFailure.vcxproj". In addition, CMake seems to invocate moc with AutomocInfo.cmake as its argument at the line 1741 in the source of CMake 2.8.12.2, "cmake.cxx". By the way, I tried to attach a file which size is 648kB but it caused server time out. Since 326kB file could be attached instantly, available size for an attached file in this system seems to be 500kB. If it is right, please change the setting of the system to be 5MB or correct the note, "Maximum size: 5,000k" in the "Upload File" section. 5MB is convenient.

(0035549) Stephen Kelly (developer) 2014-03-28 03:50	I created a trivial CMake project: cmake_minimum_required(VERSION 2.8.11) project(Foo) find_package(Qt5Core REQUIRED) set(CMAKE_AUTOMOC ON) set(CMAKE_INCLUDE_CURRENT_DIR ON) add_library(cmaketest lib.cpp) target_link_libraries(cmaketest Qt5::Core) With a simple C++ file: #include <QObject> class MyObject : public QObject { Q_OBJECT public: MyObject(QObject *parent = 0) : QObject(parent) {} }; #include "lib.moc" And I ran: set VERBOSE=1 mkdir build cd build cmake .. cmake --build . Part of the output is AUTOMOC: Checking C:/QtDev/cmaketest/lib.cpp Generating lib.moc c:/Qt/Qt5.2.0-release/5.2.0/msvc2010_opengl/bin/moc.exe -IC:/QtDev/cmaketest/ uild -IC:/QtDev/cmaketest -Ic:/Qt/Qt5.2.0-release/5.2.0/msvc2010_opengl/include -Ic:/Qt/Qt5.2.0-release/5.2.0/msvc2010_opengl/include/QtCore -Ic:/Qt/Qt5.2.0-re ease/5.2.0/msvc2010_opengl/mkspecs/win32-msvc2010 -DQT_CORE_LIB -DQT_NO_DEBUG - WIN32 -o C:/QtDev/cmaketest/build/lib.moc C:/QtDev/cmaketest/lib.cpp That is the moc command line. It is the thing we are looking for in your build. Maybe you need to set VERBOSE=1 to see the one from your build.

(0035560) Yew Kurabayashi　 (reporter) 2014-03-30 09:57 edited on: 2014-03-30 11:09	Thank you, Stephen. I have probably got what you want by your favor. The output for the command, "cmake --build ." in the build root directory is in the attached file, " commandLineOutput.txt". moc.exe is invoked from the line 51.

(0035562) Stephen Kelly (developer) 2014-03-31 04:54	You have both Qt 4 and Qt 5 includes in your command line. This probably means you have one program which links to both Qt 4 and Qt 5, which probably means your dependencies and your program have different Qt requirements. That is generally a problem. You will likely have to use one Qt version per program-and-dependencies. I was extremely surprised to find that running your moc command broke my moc executable. When I tried executing it in a Visual Studio command line window, I got a dialog telling me that "/path/to/moc.exe is not a valid Win32 application" all subsequent attempts to invoke moc.exe failed in the same way. I was extremely surprised that running an executable on Windows can break that executable until it is replaced. I added the automoc-windows-command-limit topic to next for testing. Windows seems to have a limit of 2**15 chars for commands. Using an @-file might help on Windows, but in my testing CL.exe failed anyway, for perhaps the same reason. Please test the topic.

(0035574) Stephen Kelly (developer) 2014-03-31 10:23	The patch caused a test failure so I reverted it. Please test commit 587451858f73d7585e1280de16f9d07f566fd267 and see if you hit the same CL.exe issues that I did. Then see about the test failure if the patch is otherwise correct. Thanks,

(0035581) Yew Kurabayashi　 (reporter) 2014-03-31 11:56	What should I do to reach your commit? I'm new to Git. Or is that not Git? I cloned "git://cmake.org/cmake.git" [^] and searched in it, but I couldn't find it. > I was extremely surprised that running an executable on Windows can break that executable until it is replaced. Oh, I sympathize and agree with you. I say, that's Windows! Thanks Brad, to make relation to relevant issue.

(0035584) Stephen Kelly (developer) 2014-03-31 13:19	After cloning, use 'git checkout 587451858f73d7585e1280de16f9d07f566fd267'.

(0035596) Yew Kurabayashi　 (reporter) 2014-04-01 09:24	I built both CMake 3.0.20140331-g58745 and my own solution. It looks like I got the error similar to yours. Please look in the attached file, "commandLineOutput.6.0.1.mocFailure.txt". In addition, with CMake 3.0.20140331-g58745, I got another error on the solution in which moc succeeds. The error was LNK1107 which didn't come up by CMake 2.8.12.2. Please refer to "commandLineOutput.6.0.2.mocSuccessWithLINKError.txt" for the error. I wonder if the error is from a bug of CMake 3.0.

(0035600) Stephen Kelly (developer) 2014-04-01 09:59	> I built both CMake 3.0.20140331-g58745 and my own solution. It looks like I got > the error similar to yours. Please look in the attached file, > "commandLineOutput.6.0.1.mocFailure.txt". Right. So changing automoc to use the @-file is not sufficient. > In addition, with CMake 3.0.20140331-g58745, I got another error on the > solution in which moc succeeds. The error was LNK1107 which didn't come up by > CMake 2.8.12.2. Please refer to > "commandLineOutput.6.0.2.mocSuccessWithLINKError.txt" for the error. I wonder > if the error is from a bug of CMake 3.0. It looks like the problem is that it is attempting to link to UseVTK.cmake. I don't know why it would be doing that.

(0035603) Yew Kurabayashi　 (reporter) 2014-04-01 10:21 edited on: 2014-04-01 10:46	> So changing automoc to use the @-file is not sufficient. I hope you can get a solution. Anyway, I appreciate you for your testing and advices.

(0042509) Kitware Robot (administrator) 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.

Issue History
Date Modified	Username	Field	Change
2014-03-18 00:27	Yew Kurabayashi	New Issue
2014-03-18 00:27	Yew Kurabayashi	File Added: sampleProject.zip
2014-03-18 08:45	Brad King	Note Added: 0035426
2014-03-25 11:35	Yew Kurabayashi	Note Added: 0035506
2014-03-25 11:36	Yew Kurabayashi	Tag Attached: qt
2014-03-25 11:36	Yew Kurabayashi	Tag Attached: moc
2014-03-25 11:36	Yew Kurabayashi	Tag Attached: ParaView
2014-03-25 11:39	Yew Kurabayashi	Tag Attached: CMake
2014-03-25 11:43	Yew Kurabayashi	Note Edited: 0035506
2014-03-26 08:58	Brad King	Note Added: 0035522
2014-03-26 09:08	Stephen Kelly	Note Added: 0035523
2014-03-27 03:15	Yew Kurabayashi	File Added: mocOptions.txt
2014-03-27 03:15	Yew Kurabayashi	File Added: MSVCOptions.txt
2014-03-27 03:16	Yew Kurabayashi	Note Added: 0035535
2014-03-27 03:16	Yew Kurabayashi	Note Edited: 0035535
2014-03-27 03:17	Yew Kurabayashi	Note Added: 0035536
2014-03-27 03:18	Yew Kurabayashi	Note Added: 0035537
2014-03-27 03:21	Yew Kurabayashi	Note Edited: 0035535
2014-03-27 04:30	Stephen Kelly	Note Added: 0035538
2014-03-27 05:05	Yew Kurabayashi	Note Added: 0035539
2014-03-27 05:05	Yew Kurabayashi	Note Edited: 0035539
2014-03-27 05:06	Yew Kurabayashi	Note Edited: 0035539
2014-03-27 05:23	Stephen Kelly	Note Added: 0035540
2014-03-27 05:55	Yew Kurabayashi	Note Added: 0035541
2014-03-27 06:57	Stephen Kelly	Note Added: 0035542
2014-03-28 01:37	Yew Kurabayashi	File Added: sampleProject.2.automocSuccess.without''.i''Files.zip
2014-03-28 01:38	Yew Kurabayashi	File Added: sampleProject.1.automocFailure.zip
2014-03-28 02:02	Yew Kurabayashi	Note Added: 0035545
2014-03-28 02:07	Yew Kurabayashi	Note Edited: 0035545
2014-03-28 03:50	Stephen Kelly	Note Added: 0035549
2014-03-30 09:56	Yew Kurabayashi	File Added: commandLineOutput.txt
2014-03-30 09:57	Yew Kurabayashi	Note Added: 0035560
2014-03-30 11:02	Yew Kurabayashi	Note Edited: 0035560
2014-03-30 11:09	Yew Kurabayashi	Note Edited: 0035560
2014-03-31 04:54	Stephen Kelly	Note Added: 0035562
2014-03-31 09:13	Brad King	Relationship added	related to 0014852
2014-03-31 10:23	Stephen Kelly	Note Added: 0035574
2014-03-31 11:56	Yew Kurabayashi	Note Added: 0035581
2014-03-31 13:19	Stephen Kelly	Note Added: 0035584
2014-04-01 09:19	Yew Kurabayashi	File Added: commandLineOutput.6.0.1.mocFailure.txt
2014-04-01 09:20	Yew Kurabayashi	File Added: commandLineOutput.6.0.2.mocSuccessWithLINKError.txt
2014-04-01 09:24	Yew Kurabayashi	Note Added: 0035596
2014-04-01 09:59	Stephen Kelly	Note Added: 0035600
2014-04-01 10:21	Yew Kurabayashi	Note Added: 0035603
2014-04-01 10:46	Yew Kurabayashi	Note Edited: 0035603
2016-06-10 14:29	Kitware Robot	Note Added: 0042509
2016-06-10 14:29	Kitware Robot	Status	new => resolved
2016-06-10 14:29	Kitware Robot	Resolution	open => moved
2016-06-10 14:29	Kitware Robot	Assigned To	=> Kitware Robot
2016-06-10 14:31	Kitware Robot	Status	resolved => closed