moc: Too many input files specified problem with VS 2015 and QT 5.9.6
-
I have been using VS 2015_64 on my windows 10 pc with Qt Vs tools: Qt 5.9.6.
Suddenly I am getting Mocing issues for a few files.
Error looks like this
moc: Too many input files specified: 'C:\xxx\xxx\xx\xxx\xxxxx\xxxxxxx\xxxxxxxx.h' 'IC:\xxxx\xxx\xx\xx\xx......\xx\xx\xx\xx\xxx'
1> Usage: C:\Qt\5.9.6\msvc2015_64\bin\moc.exe [options] [header-file] [@option-file]
1> Qt Meta Object Compiler version 67 (Qt 5.9.6)Also, I checked if I have spaces in my file name, but there is none.
Then for some of the files if I remove Q_OBJECT macro and put it back then I can compile those files but for some of them, it's not working. I keep on getting mocing issue.
Does anyone know what's going on? Thanks in advance.
-
I have been using VS 2015_64 on my windows 10 pc with Qt Vs tools: Qt 5.9.6.
Suddenly I am getting Mocing issues for a few files.
Error looks like this
moc: Too many input files specified: 'C:\xxx\xxx\xx\xxx\xxxxx\xxxxxxx\xxxxxxxx.h' 'IC:\xxxx\xxx\xx\xx\xx......\xx\xx\xx\xx\xxx'
1> Usage: C:\Qt\5.9.6\msvc2015_64\bin\moc.exe [options] [header-file] [@option-file]
1> Qt Meta Object Compiler version 67 (Qt 5.9.6)Also, I checked if I have spaces in my file name, but there is none.
Then for some of the files if I remove Q_OBJECT macro and put it back then I can compile those files but for some of them, it's not working. I keep on getting mocing issue.
Does anyone know what's going on? Thanks in advance.
@PoonamGupta said in moc: Too many input files specified problem with VS 2015 and QT 5.9.6:
Suddenly I am getting Mocing issues for a few files
What did you change before that started?
Did you try to delete build folder, run qmake and build? -
@jsulm ,
Hi, thanks for the reply.
I don't run Qmake. I am using Qt visual studio tool in order to build a project. Yes, I tried to do clean and build but it fails on mocing.Suddenly I am getting Mocing issues means, I am using GIT for project version control. I did pull from repository then clean complete project solution and followed by the rebuild. after this, I am not sure what cause this issues. Few members from my team don't see any issue at all, so I am not sure what's in my system creating this problem.