PDA

View Full Version : No such file or directory error on Non QT Project



franbogaz
29th November 2016, 15:53
Hi you all,

I just started to play with QT Creator using V5.7 so im newbie about all of this situations.

I'm trying to use QT just as compiler of C or C++ ; doesnt matter. I wanted to implement dot matrix lcd libraries and source files and add them to qt project. So i created a non qt project which is on C++ Plane.

I added my include and source files to project directory. I also declared them with " INCLUDEPATH += " command. Addition to i tried to add them by hand to project. I did all of these in different variations but, im getting an error and i couldnt handle it. I tried so many things which i read about this error. They were unticking the shadow building, setting building configurations etc. I really need help about that because i dont know what to do more.



There is my .pro file just concerned part:

TEMPLATE = app
CONFIG += console c++11
CONFIG -= app_bundle
CONFIG -= qt


INCLUDEPATH += "C:\ROO\\QT_Projects\\DENEME4\\inc"
INCLUDEPATH += "C:\\ROO\\QT_Projects\\DENEME4\\fonts"
INCLUDEPATH += "C:\\ROO\\QT_Projects\\DENEME4\\ssd0323"
INCLUDEPATH += "C:\\ROO\\QT_Projects\\DENEME4\\ssd0323\\cfg0323"
INCLUDEPATH += "C:\\ROO\\QT_Projects\\DENEME4\\ssd0323\\cfgio"
INCLUDEPATH += "C:\\ROO\\QT_Projects\\DENEME4\\ssd0323\\serial"
INCLUDEPATH += "C:\\ROO\\QT_Projects\\DENEME4\\ssd0323\\singlchp"

DEFINES += "GHW_NOHDW = 1"
DEFINES += "GHW_PCSIM = 1"
DEFINES += "SGPCMODE = 1"
-------------------------------------------------------------------------
Error is given below:

17:21:38: Running steps for project DENEME4...
17:21:38: Configuration unchanged, skipping qmake step.
17:21:38: Starting: "C:\Qt\Qt5.7.0\Tools\mingw530_32\bin\mingw32-make.exe"
C:\Qt\Qt5.7.0\5.7\mingw53_32\bin\qmake.exe -spec win32-g++ "CONFIG+=debug" "CONFIG+=qml_debug" -o Makefile DENEME4.pro
C:/Qt/Qt5.7.0/Tools/mingw530_32/bin/mingw32-make -f Makefile.Debug
mingw32-make[1]: Entering directory 'C:/ROO/QT_Projects/DENEME4'
g++ -c -pipe -fno-keep-inline-dllexport -g -std=gnu++11 -frtti -Wall -Wextra -fexceptions -mthreads -DUNICODE -DGHW_NOHDW = 1 -DGHW_PCSIM = 1 -DSGPCMODE = 1 -DQT_QML_DEBUG -I. -Iinc -Ifonts -Issd0323 -Issd0323\cfg0323 -Issd0323\cfgio -Issd0323\serial -Issd0323\singlchp -I..\..\..\Qt\Qt5.7.0\5.7\mingw53_32\mkspecs\win32-g++ -o debug\main.o main.cpp
g++: error: =: No such file or directory
g++: error: 1: No such file or directory
g++: error: =: No such file or directory
g++: error: 1: No such file or directory
g++: error: =: No such file or directory
g++: error: 1: No such file or directory
mingw32-make[1]: *** [debug/main.o] Error 1
mingw32-make: *** [debug] Error 2
Makefile.Debug:424: recipe for target 'debug/main.o' failed
mingw32-make[1]: Leaving directory 'C:/ROO/QT_Projects/DENEME4'
Makefile:34: recipe for target 'debug' failed
17:21:39: The process "C:\Qt\Qt5.7.0\Tools\mingw530_32\bin\mingw32-make.exe" exited with code 2.
Error while building/deploying project DENEME4 (kit: Desktop Qt 5.7.0 MinGW 32bit)
When executing step "Make"
17:21:39: Elapsed time: 00:01.

d_stranz
29th November 2016, 16:49
Remove the blank spaces from your "DEFINES" literals: DEFINES += "GHW_NOHDW=1". If you look at the arguments being passed to g++ on the command line, you'll see that your defines are mapping to "-DGHW_NOHDW = 1", which is being interpreted as 3 arguments to g++, not one.

franbogaz
29th November 2016, 20:11
Remove the blank spaces from your "DEFINES" literals: DEFINES += "GHW_NOHDW=1". If you look at the arguments being passed to g++ on the command line, you'll see that your defines are mapping to "-DGHW_NOHDW = 1", which is being interpreted as 3 arguments to g++, not one.

Thank you for your information. I cant try it now but in the morning i will try it directly. Is it only thing about this error for this case ?

Regards.

d_stranz
29th November 2016, 22:54
Is it only thing about this error for this case ?

It will fix the command line for g++, but I have no idea what errors you will run into during the rest of the compilation and linking. I don't see any libraries being linked in, for example, so you'll likely get unresolved symbol errors once you get past the compile stage and into the link stage.