Endless loop of qmake.exe
-
If you go in creator to "Projects" (left sidebar) you can see the "Build Settings". You should have "Build Steps" and "Clean Steps".
For "Build Steps" there should be two entries:
qmake: ...something...
Make: ...something...
What do the entries say?For the "Clean Step" there should be one entry.
Make: ...something...
What does it say?You can also post in addition a screenshot of that page. However, uploading of pictures is not possible here. The best thing is to use Dropbox and share a picture whose link you can post here in this box (left of link sign).
-
I cannot access dropbox from here, therefore the entries in this way:
Build steps
qmake: qmake.exe arinc2network.pro -r -spec win32-g++ "CONFIG+=debug" "CONFIG+=declarative_debug" "CONFIG+=qml_debug"qmake build configuration: Debug
Additional arguments:
Enable QML debugging: hooked
Effective qmake call: qmake.exe C:\Backups\Qt_waypoits_listed\naplps_project\arinc2network\src\arinc2network.pro -r -spec win32-g++ "CONFIG+=debug" "CONFIG+=declarative_debug" "CONFIG+=qml_debug"Make: mingw32-make.exe in C:\QT_layout_fixed\naplps_project\arinc2network\build-arinc2network-Desktop_Qt_5_1_0_MinGW_32bit-Debug
Override C:/Qt/Qt5.1.0/Tools/mingw48_32/bin/mingw32-make.exe:
Make arguments:Clean steps
Make: mingw32-make.exe clean in C:\QT_layout_fixed\naplps_project\arinc2network\build-arinc2network-Desktop_Qt_5_1_0_MinGW_32bit-DebugOverride C:/Qt/Qt5.1.0/Tools/mingw48_32/bin/mingw32-make.exe:
Make arguments: clean -
Those entries look fine to me.
Try to start the makefile from cmd.exe directly.
Open the command prompt.
@
set path=
cd C:\QT_layout_fixed\naplps_project\arinc2network\build-arinc2network-Desktop_Qt_5_1_0_MinGW_32bit-Debug
C:/Qt/Qt5.1.0/Tools/mingw48_32/bin/mingw32-make.exe
@
The first statement clears your path to avoid side effects.
Certainly you can go step by step to the shadow folder "build-arinc2network-Desktop_Qt_5_1_0_MinGW_32bit-Debug".
You should find the "Makefile" there. This would be started with "mingw32-make". -
Hey,
thanks for your help.I confused two of my backups in my last post. Both directories are of course:
C:\Backups\Qt_waypoits_listed...Now I set the path to the debug folder and ran make.exe asyou discribed.
As output I get the same problem as when building or cleaning a project:@C:/Qt/Qt5.1.0/5.1.0/mingw48_32/bin/qmake.exe -spec win32-g++ CONFIG+=debug CONFIG+=declarative_debug CONFIG+=qml_debug -o Makefile ../src/arinc2network.pro@
This is posted on and on.In the folder are a Makefile, a Makefile.Debug and a Makefile.Release.
The text in the Makefile is the following:
@#############################################################################Makefile for building: arinc2network
Generated by qmake (3.0) (Qt 5.1.0) on: So 31. Mrz 10:37:40 2013
Project: ..\src\arinc2network.pro
Template: app
Command: C:\Qt\Qt5.1.0\5.1.0\mingw48_32\bin\qmake.exe -spec win32-g++ CONFIG+=debug CONFIG+=declarative_debug CONFIG+=qml_debug -o Makefile ..\src\arinc2network.pro
#############################################################################
MAKEFILE = Makefile
first: debug
install: debug-install
uninstall: debug-uninstall
QMAKE = C:\Qt\Qt5.1.0\5.1.0\mingw48_32\bin\qmake.exe
DEL_FILE = del
CHK_DIR_EXISTS= if not exist
MKDIR = mkdir
COPY = copy /y
COPY_FILE = $(COPY)
COPY_DIR = xcopy /s /q /y /i
INSTALL_FILE = $(COPY_FILE)
INSTALL_PROGRAM = $(COPY_FILE)
INSTALL_DIR = $(COPY_DIR)
DEL_FILE = del
SYMLINK = copy /y
DEL_DIR = rmdir
MOVE = move
SUBTARGETS =
debug
releasedebug: FORCE
$(MAKE) -f $(MAKEFILE).Debug
debug-make_first: FORCE
$(MAKE) -f $(MAKEFILE).Debug
debug-all: FORCE
$(MAKE) -f $(MAKEFILE).Debug all
debug-clean: FORCE
$(MAKE) -f $(MAKEFILE).Debug clean
debug-distclean: FORCE
$(MAKE) -f $(MAKEFILE).Debug distclean
debug-install: FORCE
$(MAKE) -f $(MAKEFILE).Debug install
debug-uninstall: FORCE
$(MAKE) -f $(MAKEFILE).Debug uninstall
release: FORCE
$(MAKE) -f $(MAKEFILE).Release
release-make_first: FORCE
$(MAKE) -f $(MAKEFILE).Release
release-all: FORCE
$(MAKE) -f $(MAKEFILE).Release all
release-clean: FORCE
$(MAKE) -f $(MAKEFILE).Release clean
release-distclean: FORCE
$(MAKE) -f $(MAKEFILE).Release distclean
release-install: FORCE
$(MAKE) -f $(MAKEFILE).Release install
release-uninstall: FORCE
$(MAKE) -f $(MAKEFILE).Release uninstallMakefile: ../src/arinc2network.pro C:/Qt/Qt5.1.0/5.1.0/mingw48_32/mkspecs/win32-g++/qmake.conf C:/Qt/Qt5.1.0/5.1.0/mingw48_32/mkspecs/features/spec_pre.prf
C:/Qt/Qt5.1.0/5.1.0/mingw48_32/mkspecs/qdevice.pri
C:/Qt/Qt5.1.0/5.1.0/mingw48_32/mkspecs/features/device_config.prf \(...lots of .pri and .prf data)
C:/Qt/Qt5.1.0/5.1.0/mingw48_32/mkspecs/features/testcase_targets.prf
C:/Qt/Qt5.1.0/5.1.0/mingw48_32/mkspecs/features/exceptions.prf
C:/Qt/Qt5.1.0/5.1.0/mingw48_32/mkspecs/features/yacc.prf
C:/Qt/Qt5.1.0/5.1.0/mingw48_32/mkspecs/features/lex.prf
../src/arinc2network.pro
C:/Qt/Qt5.1.0/5.1.0/mingw48_32/lib/Qt5Network.prl
C:/Qt/Qt5.1.0/5.1.0/mingw48_32/lib/Qt5Core.prl
$(QMAKE) -spec win32-g++ CONFIG+=debug CONFIG+=declarative_debug CONFIG+=qml_debug -o
Makefile ..\src\arinc2network.pro
C:\Qt\Qt5.1.0\5.1.0\mingw48_32\mkspecs\features\spec_pre.prf:
C:\Qt\Qt5.1.0\5.1.0\mingw48_32\mkspecs\qdevice.pri:(...lots of .pri and .prf data)
C:\Qt\Qt5.1.0\5.1.0\mingw48_32\mkspecs\features\yacc.prf:
C:\Qt\Qt5.1.0\5.1.0\mingw48_32\mkspecs\features\lex.prf:
..\src\arinc2network.pro:
C:/Qt/Qt5.1.0/5.1.0/mingw48_32/lib/Qt5Network.prl:
C:/Qt/Qt5.1.0/5.1.0/mingw48_32/lib/Qt5Core.prl:
qmake: FORCE
@$(QMAKE) -spec win32-g++ CONFIG+=debug CONFIG+=declarative_debug CONFIG+=qml_debug -o Makefile ..\src\arinc2network.proqmake_all: FORCE
make_first: debug-make_first release-make_first FORCE
all: debug-all release-all FORCE
clean: debug-clean release-clean FORCE
distclean: debug-distclean release-distclean FORCE
-$(DEL_FILE) Makefiledebug-mocclean:
$(MAKE) -f $(MAKEFILE).Debug mocclean
release-mocclean:
$(MAKE) -f $(MAKEFILE).Release mocclean
mocclean: debug-mocclean release-moccleandebug-mocables:
$(MAKE) -f $(MAKEFILE).Debug mocables
release-mocables:
$(MAKE) -f $(MAKEFILE).Release mocables
mocables: debug-mocables release-mocablescheck: first
FORCE:$(MAKEFILE).Debug: Makefile
$(MAKEFILE).Release: Makefile
@ -
What is in the top section of the makefile.Debug aside of the makefile you have posted. That section gives you the compiler, options and tools
-
@#############################################################################
Makefile for building: arinc2network
Generated by qmake (3.0) (Qt 5.1.0) on: So 31. Mrz 11:34:07 2013
Project: ../src/arinc2network.pro
Template: app
#############################################################################
MAKEFILE = Makefile.Debug
####### Compiler, tools and options
CC = gcc
CXX = g++
DEFINES = -DUNICODE -DQT_QML_DEBUG -DQT_DECLARATIVE_DEBUG -DQT_NETWORK_LIB -DQT_CORE_LIB
CFLAGS = -pipe -fno-keep-inline-dllexport -g -Wall -Wextra $(DEFINES)
CXXFLAGS = -pipe -fno-keep-inline-dllexport -g -frtti -Wall -Wextra -fexceptions -mthreads $(DEFINES)
INCPATH = -I../src -I'../../advTcpSocket' -I'../../socketConfig' -I'../../aimCard/src' -I'../../aimCard/src/third_part/aim' -I'../../arincChannel' -I'../../condorCard/src' -I'../../condorCard/src/third_part/condor/include' -I'../../advTcpServer' -I'C:/Qt/Qt5.1.0/5.1.0/mingw48_32/include' -I'C:/Qt/Qt5.1.0/5.1.0/mingw48_32/include/QtNetwork' -I'C:/Qt/Qt5.1.0/5.1.0/mingw48_32/include/QtCore' -I'debug' -I'.' -I'C:/Qt/Qt5.1.0/5.1.0/mingw48_32/mkspecs/win32-g++'
LINKER = g++
LFLAGS = -Wl,-subsystem,console -mthreads
LIBS = -LC:/Backups/Qt_waypoits_listed/naplps_project/arinc2network/src/../../aimCard/src/third_part/aim/libs -LC:/Backups/Qt_waypoits_listed/naplps_project/arinc2network/src/../../condorCard/src/third_part/condor/libs -LC:/Backups/Qt_waypoits_listed/naplps_project/arinc2network/src/../../condorCard/src/third_part/condorLib-build-desktop/debug/ -lcondorLib -lapi_civ -lcei_ll -lwinmm -LC:\Qt\Qt5.1.0\5.1.0\mingw48_32\lib -lQt5Networkd -lQt5Cored
QMAKE = C:/Qt/Qt5.1.0/5.1.0/mingw48_32/bin/qmake.exe
IDC = idc
IDL = midl
ZIP =
DEF_FILE =
RES_FILE =
COPY = cp -f
SED = sed
COPY_FILE = cp -f
COPY_DIR = cp -f -R
DEL_FILE = rm -f
DEL_DIR = rmdir
MOVE = mv -f
CHK_DIR_EXISTS= test -d
MKDIR = mkdir -p
INSTALL_FILE = cp -f
INSTALL_PROGRAM = cp -f
INSTALL_DIR = $(COPY_DIR)
@ -
further done in the file you should something like
@
clean: compiler_clean
-$(DEL_FILE) ... long list of objects ...
@in the compile section
@
bliblo.o: ../../ ..... blobli.cpp ../../ .... blobli.h
list of other headers
$(CXX) -c $(CXXFLAGS) $(INCPATH) -o blobli.o blobli.cpp
@Note: I have shortened the path considerably. The important part after each object is the $(CXX) plus subsequent stuff.
-
I have following parts in the Makefile.Debug:
@clean: compiler_clean
-$(DEL_FILE) debug/main.o debug/socketconfig.o debug/advtcpsocket.o debug/aimcard.o debug/condorcard.o debug/arincChannel.o debug/advtcpserver.o debug/moc_advtcpsocket.o debug/moc_aimcard.o debug/moc_condorcard.o debug/moc_arincChannel.o debug/moc_advtcpserver.o@
Also I have the $(CXX) plus subsequent stuff in the compile section for every header/source pair I add in my .pro file I removed the other headers for the post.
I do not have a moc_socketconfig.o entry, but I do not know, if this is a problem@####### Compile
debug/main.o: ../src/main.cpp C:/Qt/Qt5.1.0/5.1.0/mingw48_32/include
...
$(CXX) -c $(CXXFLAGS) $(INCPATH) -o debug/main.o ../src/main.cppdebug/socketconfig.o: ../../socketConfig/socketconfig.cpp ../../socketConfig/socketconfig.h
...
$(CXX) -c $(CXXFLAGS) $(INCPATH) -o debug/socketconfig.o ../../socketConfig/socketconfig.cppdebug/advtcpsocket.o: ../../advTcpSocket/advtcpsocket.cpp ../../advTcpSocket/advtcpsocket.h
...
$(CXX) -c $(CXXFLAGS) $(INCPATH) -o debug/advtcpsocket.o ../../advTcpSocket/advtcpsocket.cppdebug/aimcard.o: ../../aimCard/src/aimcard.cpp ../../aimCard/src/aimcard.h
...
$(CXX) -c $(CXXFLAGS) $(INCPATH) -o debug/aimcard.o ../../aimCard/src/aimcard.cppdebug/condorcard.o: ../../condorCard/src/condorcard.cpp ../../condorCard/src/condorcard.h
...
$(CXX) -c $(CXXFLAGS) $(INCPATH) -o debug/condorcard.o ../../condorCard/src/condorcard.cppdebug/arincChannel.o: ../../arincChannel/arincChannel.cpp ../../arincChannel/arincChannel.h
...
$(CXX) -c $(CXXFLAGS) $(INCPATH) -o debug/arincChannel.o ../../arincChannel/arincChannel.cppdebug/advtcpserver.o: ../../advTcpServer/advtcpserver.cpp
...
$(CXX) -c $(CXXFLAGS) $(INCPATH) -o debug/advtcpserver.o ../../advTcpServer/advtcpserver.cppdebug/moc_advtcpsocket.o: debug/moc_advtcpsocket.cpp
$(CXX) -c $(CXXFLAGS) $(INCPATH) -o debug/moc_advtcpsocket.o debug/moc_advtcpsocket.cppdebug/moc_aimcard.o: debug/moc_aimcard.cpp
$(CXX) -c $(CXXFLAGS) $(INCPATH) -o debug/moc_aimcard.o debug/moc_aimcard.cppdebug/moc_condorcard.o: debug/moc_condorcard.cpp
$(CXX) -c $(CXXFLAGS) $(INCPATH) -o debug/moc_condorcard.o debug/moc_condorcard.cppdebug/moc_arincChannel.o: debug/moc_arincChannel.cpp
$(CXX) -c $(CXXFLAGS) $(INCPATH) -o debug/moc_arincChannel.o debug/moc_arincChannel.cppdebug/moc_advtcpserver.o: debug/moc_advtcpserver.cpp
$(CXX) -c $(CXXFLAGS) $(INCPATH) -o debug/moc_advtcpserver.o debug/moc_advtcpserver.cpp@ -
Frankly, I am running out of ideas by now.
When you are starting mingw32-make from cmd.exe with parameter "--version" what does it tell you?
-
Following text is displayed when runing with "--version". Nothing else is executed.
@GNU Make 3.82.90
Built for i686-w64-mingw32
Copyright <C> 1988-2012 Free Software Foundation, Inc.
License GPLv3+:GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is No WARRANTY, to extent permitted by law.@I have no clue, what has happend to my QtCreator. The error occured after I was running qmake. Afterwards none of my projects, also the backups cannot be build or cleaned anymore, thoug they still work on a other computer. After running qmake and building successfully on a other computer, I can even run on this computer, as long as the 'Configuration unchanged, skipping qmake step.'
Unfortunatly the application does not changeif I then make any changes in the code. And after I run qmake, which is successful, I cannot build any more with the old problem.
Reinstalling Qt did not solve the problem either. -
Well, you wrote that starting mingw32-make on the command show the same problem. This is a bit strange. This means that the makefile is wrong. Which is generated by qmake.
Since you can produce a makefile on the still working pc, you can compare the makefiles.
If you have the setup (versions and folders) you can take over the qmake from pc to the other. Make a copy of qmake before you copy the version over it. -
I have compared the makefiles using kdiff and found some differences:
Makefile (from reference computer)
@QMAKE = C:/Qt/Qt5.1.0/5.1.0/mingw48_32/bin/qmake.exe
DEL_FILE = rm -f
CHK_DIR_EXISTS= test -d
MKDIR = mkdir -p
COPY = cp -f
COPY_FILE = cp -f
COPY_DIR = cp -f -R
INSTALL_FILE = cp -f
INSTALL_PROGRAM = cp -f
INSTALL_DIR = $(COPY_DIR)
DEL_FILE = rm -f
SYMLINK =
DEL_DIR = rmdir
MOVE = mv -f
SUBTARGETS = @Makefile (from defecte computer)
@QMAKE = C:\Qt\Qt5.1.0_new\5.1.0\mingw48_32\bin\qmake.exe
DEL_FILE = del
CHK_DIR_EXISTS= if not exist
MKDIR = mkdir
COPY = copy /y
COPY_FILE = $(COPY)
COPY_DIR = xcopy /s /q /y /i
INSTALL_FILE = $(COPY_FILE)
INSTALL_PROGRAM = $(COPY_FILE)
INSTALL_DIR = $(COPY_DIR)
DEL_FILE = del
SYMLINK = copy /y
DEL_DIR = rmdir
MOVE = move
SUBTARGETS = @Makefile.Debug (from defect computer)
@
####### Compiler, tools and optionsCC = gcc
CXX = g++
DEFINES = -DUNICODE -DQT_QML_DEBUG -DQT_DECLARATIVE_DEBUG -DQT_NETWORK_LIB -DQT_CORE_LIB
CFLAGS = -pipe -fno-keep-inline-dllexport -g -Wall -Wextra $(DEFINES)
CXXFLAGS = -pipe -fno-keep-inline-dllexport -g -frtti -Wall -Wextra -fexceptions -mthreads $(DEFINES)
INCPATH = -I..\src -I"....\advTcpSocket" -I"....\socketConfig" -I"....\aimCard\src" -I"....\aimCard\src\third_part\aim" -I"....\arincChannel" -I"....\condorCard\src" -I"....\condorCard\src\third_part\condor\include" -I"....\advTcpServer" -I"....\Font" -I"C:\Qt\Qt5.1.0_new\5.1.0\mingw48_32\include" -I"C:\Qt\Qt5.1.0_new\5.1.0\mingw48_32\include\QtNetwork" -I"C:\Qt\Qt5.1.0_new\5.1.0\mingw48_32\include\QtCore" -I"debug" -I"." -I"C:\Qt\Qt5.1.0_new\5.1.0\mingw48_32\mkspecs\win32-g++"
LINKER = g++
LFLAGS = -Wl,-subsystem,console -mthreads
LIBS = "-LC:/Documents and Settings/etzmcn/Bureau/Qt_latest/naplps_project/arinc2network/src/../../condorCard/src/third_part/condorLib-build-desktop/debug/" -lcondorLib "-LC:/Documents and Settings/etzmcn/Bureau/Qt_latest/naplps_project/arinc2network/src/../../aimCard/src/third_part/aim/libs" -lapi_civ "-LC:/Documents and Settings/etzmcn/Bureau/Qt_latest/naplps_project/arinc2network/src/../../condorCard/src/third_part/condor/libs" -lcei_ll -lwinmm -LC:\Qt\Qt5.1.0_new\5.1.0\mingw48_32\lib -lQt5Networkd -lQt5Cored
QMAKE = C:\Qt\Qt5.1.0_new\5.1.0\mingw48_32\bin\qmake.exe
IDC = idc
IDL = midl
ZIP = zip -r -9
DEF_FILE =
RES_FILE =
COPY = copy /y
SED =
COPY_FILE = $(COPY)
COPY_DIR = xcopy /s /q /y /i
DEL_FILE = del
DEL_DIR = rmdir
MOVE = move
CHK_DIR_EXISTS= if not exist
MKDIR = mkdir
INSTALL_FILE = $(COPY_FILE)
INSTALL_PROGRAM = $(COPY_FILE)
INSTALL_DIR = $(COPY_DIR)####### Output directory
OBJECTS_DIR = debug@
Makefile.Debug (from referencecomputer)
@
####### Compiler, tools and optionsCC = gcc
CXX = g++
DEFINES = -DUNICODE -DQT_QML_DEBUG -DQT_DECLARATIVE_DEBUG -DQT_NETWORK_LIB -DQT_CORE_LIB
CFLAGS = -pipe -fno-keep-inline-dllexport -g -Wall -Wextra $(DEFINES)
CXXFLAGS = -pipe -fno-keep-inline-dllexport -g -frtti -Wall -Wextra -fexceptions -mthreads $(DEFINES)
INCPATH = -I../src -I'../../advTcpSocket' -I'../../socketConfig' -I'../../aimCard/src' -I'../../aimCard/src/third_part/aim' -I'../../arincChannel' -I'../../condorCard/src' -I'../../condorCard/src/third_part/condor/include' -I'../../advTcpServer' -I'../../Font' -I'C:/Qt/Qt5.1.0/5.1.0/mingw48_32/include' -I'C:/Qt/Qt5.1.0/5.1.0/mingw48_32/include/QtNetwork' -I'C:/Qt/Qt5.1.0/5.1.0/mingw48_32/include/QtCore' -I'debug' -I'.' -I'C:/Qt/Qt5.1.0/5.1.0/mingw48_32/mkspecs/win32-g++'
LINKER = g++
LFLAGS = -Wl,-subsystem,console -mthreads
LIBS = -LC:/Qt_gui_desktop_working/naplps_project/arinc2network/src/../../aimCard/src/third_part/aim/libs -LC:/Qt_gui_desktop_working/naplps_project/arinc2network/src/../../condorCard/src/third_part/condor/libs -LC:/Qt_gui_desktop_working/naplps_project/arinc2network/src/../../condorCard/src/third_part/condorLib-build-desktop/debug/ -lcondorLib -lapi_civ -lcei_ll -lwinmm -LC:\Qt\Qt5.1.0\5.1.0\mingw48_32\lib -lQt5Networkd -lQt5Cored
QMAKE = C:/Qt/Qt5.1.0/5.1.0/mingw48_32/bin/qmake.exe
IDC = idc
IDL = midl
ZIP =
DEF_FILE =
RES_FILE =
COPY = cp -f
SED = sed
COPY_FILE = cp -f
COPY_DIR = cp -f -R
DEL_FILE = rm -f
DEL_DIR = rmdir
MOVE = mv -f
CHK_DIR_EXISTS= test -d
MKDIR = mkdir -p
INSTALL_FILE = cp -f
INSTALL_PROGRAM = cp -f
INSTALL_DIR = $(COPY_DIR)####### Output directory
OBJECTS_DIR = debug/
@
Also are there a lot of backslash and slash differences!
Furthermore I am currently able to use one of my projects on the defect computer after building it successfully on another one. I can build clean and run qmake without problems, though I have no clue, why this project works now.
Unfortunatly all other projects do either not run at all, or do not runafter I made qmake on the defect computer. -
backslashes could be the problem.
Checkout on the "defect" setup computer your .pro files.
DO NOT use backslashes in Qt related for folders. They have a special meaning and mark that the next line is a continuation line.
A .pro file should have statements like:
@
HEADERS += ./head.h
./head2.h
c:/AnotherHeader/header3.h
c:/Blo/bli.h
@As you see at the end of lines there is a backslash when another line is following.
-
Yes, but I have used the same .pro file on both computers, without changing it. And if I open the .pro file on the defect computer, everything looks fine:
@#-------------------------------------------------Project created by QtCreator 2011-11-17T11:31:42
#-------------------------------------------------
QT += core
QT -= gui
QT += network
TARGET = arinc2network
CONFIG += console
CONFIG -= app_bundleTEMPLATE = app
INCLUDEPATH += ../../advTcpSocket/
../../socketConfig/
../../aimCard/src/
../../aimCard/src/third_part/aim/
../../arincChannel/
../../condorCard/src/
../../condorCard/src/third_part/condor/include/
../../advTcpServer/
../../Font/CONFIG += console
SOURCES += main.cpp
../../socketConfig/socketconfig.cpp
../../advTcpSocket/advtcpsocket.cpp
../../aimCard/src/aimcard.cpp
../../condorCard/src/condorcard.cpp
../../arincChannel/arincChannel.cpp
../../advTcpServer/advtcpserver.cppHEADERS +=
../../socketConfig/socketconfig.h
../../advTcpSocket/advtcpsocket.h
../../aimCard/src/aimcard.h
../../condorCard/src/condorcard.h
../../napArray/napArray.h
../../arincChannel/arincChannel.h
../../advTcpServer/advtcpserver.hLIBS += -L"$$PRO_FILE_PWD/../../aimCard/src/third_part/aim/libs" -lapi_civ
-L"$$PRO_FILE_PWD/../../condorCard/src/third_part/condor/libs" -lcei_ll -lwinmmCONFIG(debug) {
LIBS += -L"$$PRO_FILE_PWD/../../condorCard/src/third_part/condorLib-build-desktop/debug/" -lcondorLib
-L"$$PRO_FILE_PWD/../../aimCard/src/third_part/aim/libs" -lapi_civ
-L"$$PRO_FILE_PWD/../../condorCard/src/third_part/condor/libs" -lcei_ll -lwinmm
}
@ -
Did you copy the qmake from one machine to the other?
Do not forget the safety copy!Are both OS identical?
Any OS language settings? Which are different? -
I have copied the whole project from one pc to the other. I could not build it, then I ran qmake and could again not build it. The I compared the new makefile with the backup.Unfortunatly are the backslashes created by the computer, that is working fine. The "correct" slashes are created by the computer that is getting the endless loop.
The problem is, that I cannot even reproduce the behaviour. I have some older makefiles from the "working" computer, which have no false baskslashes. This morning I tried and it made backslashes in the path. Still building the project worked fine. Sometimes I can build the project on the defect PC (when creating the makefile is skipped - the configuration has not changed) when I copy it from the working pc, sometimes the endless build occurs and sometimes I get Makefile Error 2 message. And the one file I copied can be build even after I run qmake on the defect PC.
Both OS are a french windows xp version. Qt is both times english and version 5.1.0
-
It could be windows xp possibly in combination with french. However, this is for sure trying hit something in the fog. :(
Qt libs are English anyway. You can change the language setting in Qt creator, but that should not matter I would think. default installations were in German in my case. I have changed merely because I used to have English interfaces and get irritated by German :)The only thing you have apparently not tried (or I have not found) is copying the QMAKE.EXE version from one installation to the other.
However, once again, make sure that you have a safety copy in order to be able to restore.
As long as you have the identical setup (folder names and stuff) on both machines, this should be possible.
The executable QMAKE.EXE is most likely the trouble maker.However, IMHO all is very illogical!!
If there are some issues with xp and new Qt creator respectively qmake, I cannot answer. I do not have the experience.
You would have to raise this question with the developer channel. -
Thank you again for your help.
I copied qmake.exe from the other computer and building and cleaning works fine now!
The only strange behaviour is, that I have to run qmake before building in order to get my sourcecode changes compiled. But this at least, is a behaviour I can live with! -
[quote author="Benjamin05" date="1375429902"]
I copied qmake.exe from the other computer and building and cleaning works fine now!
[/quote]
That is good to know.[quote author="Benjamin05" date="1375429902"]
The only strange behaviour is, that I have to run qmake before building in order to get my sourcecode changes compiled. But this at least, is a behaviour I can live with![/quote]
I got this behavior too. When switching between release and debug compilations, I need to run qmake for sure.
I have quite complex projects using "subdirs" templates. Editing in the subprojects is not always caught properly and caused already a couple of times heavy swearing ;-) -
Had the same behavior. I had a cross-compile environment building for Raspberry Pi. The reason for that behavior was, that the clock of the embedded system was hours late. That's why "make" resulted in calling "qmake" forever...