Tool Removal Steps Returned Error Code From Moc Mainwindow.h Problem
Tool Removal Steps Returned Error Code From Moc Mainwindow.h Problem
Approved: ASR Pro
Sometimes your computer may generate an error indicating that the tool returned an error code from moc mainwindow.h. There can be several reasons for this problem.
I have configured a build location for a number of C ++ projects in Visual Studio that use Qt. does not work any more.
As far as I know, all environment variables are still correct and I have not informed Visual Studio or Qt.
1> MOC mainwindow.h1> The product cannot find the path specified.1> moc: mainwindow.h: no file of this type1> Project: Error PRJ0019: Tool returned error and area code "MOC mainwindow.h"
C: QtSDK Desktop Qt 4.8.1 msvc2008 bin moc.exe -DUNICODE -DQT_LARGEFILE_SUPPORT -dwin32 -DQT_DLL -DQT_GUI_LIB -DQT_COREKS_LIB-DesktopXAVE DQT_COREKS_LIB -DQAVT_SSXQS_LIB -DQAVT_SSQSQSQSQS_LIB -DQAVT_SSXQS_LIB. T DKS Qt 4.8.1 msvc2008 include QtCore "-I" .. .. .. .. QtSDK Desktop Qt 4.8.1 msvc2008 include QtGui "- I ".. .. .. .. QtSDK Desktop Qt 4.8.1 msvc2008 include" -I ".. .. LSL liblsl bin" -I ". ... .. .. .. QtSDK Desktop Qt 4.8.1 msvc2008 include ActiveQt "-I" debug "-I". "-I .. .. .. .. QtSDK Desktop Qt 4.8.1 msvc2008 mkspecs default -D_MSC_VER = 1500 -DWIN32 mainwindow.h -o debug moc_mainwindow.cpp
(Sorry, too long). This shows that moc.exe is being called very often, but it cannot acquire mainwindow.h (which is in the project website directory and is definitely an included directory).
I re-run qmake -project
qmake (thanks J-Mik!) but it depends on the userabout interface
1> UIC mainwindow.ui1> The system cannot find the specified route.1> File mainwindow.ui is not valid1> Project Error PRJ0019: The tool returned a valid error code "UIC mainwindow.ui".
File made safe and valid (opens in Creator) qt. It is also considered odd that the build log keeps writing the error moc:
C: QtSDK Desktop Qt 4.8.1 msvc2008 bin moc.exe -DUNICODE -DQT_LARGEFILE_SUPPORT -dwin32 -DQT_DLL -DQT_GUI_LIB -DQT_COREKS_LIB-DesktopXAVE DQT_COREKS_LIB -DQAVT_SSXQS_LIB -DQAVT_SSQSQSQSQS_LIB -DQAVT_SSXQS_LIB. T DKS Qt 4.8.1 msvc2008 include QtCore "-I" .. .. .. .. QtSDK Desktop Qt 4.8.1 msvc2008 include QtGui "- I ".. .. .. .. QtSDK Desktop Qt 4.8.1 msvc2008 include" -I ".. .. LSL liblsl bin" -I ". ... .. .. .. QtSDK Desktop Qt 4.8.1 msvc2008 include ActiveQt "-I" debug "-I". "-I .. .. .. .. QtSDK Desktop Qt 4.8.1 msvc2008 mkspecs default -D_MSC_VER = 1500 -DWIN32 mainwindow.h -u debug moc_mainwindow.cppif errorlevel 1 goto VCReportErrorgo to VCEnd project: VCReportErrorecho: error PRJ0019: device returned error code caused by "MOC mainwindow.h"Exit 1: VCEnd
I have several projects that I haven't compiled on one netbook for a long time, although they do well with others - exactly the same projects, without copies. The compilation code comes from the same “network catalog. As I said, it works fine on some computers.
However, the visual school on all computers in my office seems to have completely lost the directory structure smell.
I first had problems with moc (these assemblies use Qt) when I first found the mainwindow.h suggestion. It is in the above directory as .sln, .vproj, etc. I asked a question about this ribbon here:Visual Studio 2008 cannot find mainwindow.h
By deleting and reloading the main window. In b, the project, moc and visual company could see it.
Moc can now find mainwindow.h, uic, but mainwindow.ui is hard to find, which is not surprising in this regard. This is a Visual Studio error Get what I:
1> UIC mainwindow.ui1> The installer cannot find the path specified.1> File mainwindow.ui is invalid1> Project Error PRJ0019: Tool returned error code "UIC mainwindow.ui"
C: QtSDK Desktop Qt 4.8.1 msvc2008 bin uic.exe mainwindow.ui -o ui_mainwindow.h
In the case where I put the solution contained in the cd directory I have the option to run this line above and so it will generate ui_mainwindow just fine.
I am real I feel lost here. Obviously the above file permissions are fine for me as I can compile them (but not through my local copy of Sight Studio). Obviously the .vcproj files are fine, most likely because I can compile on multiple other machines. It looks like there are some general path adjustments that I accidentally made to my personal copy of the studio visual. I
Also, I reinstalled it and it still meets the requirements. I thought that if there was some nasty config file before that that kept the file structure secret on Windows, it would have already cleared the file, but as you can imagine, this did not happen.
On a computer running this configuration, the first conclusion is obvious:
1> UIC mainwindow.ui1> Z: dmedine git-lsl-tst-wrkng labstreaminglayer Apps XDFBrowser> doskey python26 = "C: python26 python"1> MOC mainwindow.h1> Z: dmedine git-lsl-tst-wrkng labstreaminglayer Apps XDFBrowser> doskey python26 = "C: python26 python"
I'm a little confused here by some of the Doskey commands (I haven't created all of these projects, so there is a lot to really confuse). Do you need Moc Python for Windows in additionhow to uic? I've been experimenting lately with my favorite Python-related Doskeys, maybe it's precious and the root of the job, but I'd like to understand why.
As I suspected, it was actually a key I added to regedit that might have aliases to invoke special versions of Python. This folder is here (in case anyone is interested):
doskey ls = dir python27-64 = C: Python27-64 python $ *doskey.exe $ *doskey python35-32 = C: python35-32 python.exe $ *
Apparently (and I only noticed this when I was checking each working config and ticking each of our lines) connect these calls to doskey to get rid of the moc / ui process on Windows.
This makes no sense. Also, it has always been quite inconvenient since I am working very hard now to get different versions of Python.Get the best performance from your computer with this software - download it and fix your PC today.
Les Escabeaux De Retrait D'outils Ont Renvoyé Un Code D'erreur Du Problème Moc Mainwindow.h
Trappor För Borttagning Av Verktyg Returnerade Felkod Från Moc Mainwindow.h Problem
I Passaggi Per La Rimozione Dello Strumento Tornano Al Codice Di Errore Da Moc Mainwindow.h Problema
Aktivitäten Zum Entfernen Von Tools Haben Einen Fehlercode Von Moc Mainwindow.h Zurückgegeben Problem
Kroki Usuwania Narzędzia Spowodowały Powrót Kodu Błędu Z Moc Mainwindow.h Problem
Действия по удалению инструмента возвращают код ошибки из Moc Mainwindow.h Проблема
Stappen Voor Het Verwijderen Van Gereedschap Hebben Een Foutcode Geretourneerd Op Moc Mainwindow.h Probleem
도구 제거 단계에서 Moc Mainwindow.h 문제에 의해 발생한 오류 코드를 반환했습니다.
As Etapas De Remoção Da Ferramenta Devolveram O Código De Erro Do Moc Mainwindow.h Problema
Los Pasos De Eliminación De Herramientas Devolvieron Software De Error De Moc Mainwindow.h Problema