Hello! Updating from my side.
Thank you @SGaist for your answer, for future people facing the same issue: I did not have any uncommon character in the paths more than underscores.

My fix:
I figured with some help and testing deploying to other folder structures that qmake was the problem and complaining.
Placing the whole project one level up (C:\Repos\NewLevel\ ...) fixed the issue and no problem from Qt whatsoever.

It is purely a workaround that Qt seems to be ok with. As my version control begins after NewLevel, it is also not an issue. Maybe I will try in the future to take it down one level after some update in Qt, but AFAIK it is not a reported bug.
As I said, other machines with identical Project Strcture using same Qt Version and QtCreator seemed to be okay with that. The Makefiles look also the same in terms of relative paths.

@Leoo Please post your pro file (as text not pictures).

I solved it, the makefile contains this command as well:

flex MyLanguage.l

and in the OS there is two intalled flex, Qt used the wrong one.

I don't know why, but it seems when I use Qt creator class definition tool, In my project's .pro file, In 'SOURCES' and 'HEADERS' part, it makes all .cpp and .h files except the two new files I've added to the project.
By commenting the code that excludes these files in .pro, problem solved.

If you did something like

CONFIG = debug

You, in fact, nuked the content of the variable and replaced it with debug.

If you want to modify the content of such a variable, use either += or *=. The first to add a value and the second to add the value only if not already in the variable.

@Kinesis

There are only two options:

Install a compatible Qt version on the second computer Deploy all needed libraries along with your program. You may want to have a look at linuxdeployqt

Regards

@VRonin said in QCA no Makefile:

also, if you are using MSVC you have to tell cmake to generate makefiles instead of project files. Pass the -G "NMake Makefiles" arguments to your cmake call

You sir, have saved me. I can't believe they don't specify that in the guide (it also uses MSVC, so idk why there wasn't the same problem).

I've run into some trouble while building, but that can/should be its own topic.

@VRonin said in QCA no Makefile:

Slightly related, is QCA supported and updated? The last thing you'd want is to use an out of date cryptographic library.

I normally use Crypto++ but libcrypto of OpenSSL is also very good (if you don't mind messing with C)

It is still active, looking at the the git (https://cgit.kde.org/qca.git/) the last commit was in 2017-09-30 (some months ago, but it isn't dead).
I had also been looking at Crypto++, but ended up settleing for QCA for no pacticular reasons. And I wouldn't mess with C, I'm still even just a C++ newbie afterall ;) QCA can also use OpenSSL btw.

@JKSH said in MinGW Makefile project in QtCreator:

Qt Creator does not call the compiler directly. It simply calls mingw32-make.exe and tells it which Makefile to use.

mingw32-make.exe is the one that calls the compiler (g++.exe). The Makefile does not contain the absolute path to the compiler, so it searches your system environment to find g++.exe.

Ah ok, it makes sense.
So far, the only way might be QtCreator should add to the sys env of the shell the path of the selected compiler. But perhaps they rely on the knowledge of the users :)

@raven-worx said:

$(MAKE)

Awesome, that worked. Thank you!

Hi,

Do you have all dependencies accessible ? As you would need for a deployment.

Hi,

Don't try to re-use Makefiles from Linux on Windows. You have your .pro file so open your project with Qt Creator and built it there.

Found the solution.

So I ran qmake with -d to get debug output. In there I could see the extra libpath came from msvc2012_opengl\lib\qtmain.prl that has a setting QMAKE_PRL_LIBS. The path to Qt5Core is for some reason hardcoded there and in my case it was incorrect. Still unsure why it was incorrect but editing it solved it for me.

Hi,

Windows 64 bit is able to run 32bit applications. What exact error do you get ? Did you setup all android environment variables ?

@SGaist
Hi,
thanks, it works.

Later to that,

I have figured out a problem in having:

We need to have \" in the argument:
-DBOO_PATH="/path/to/boost"
Problem is that, the macro turned out to be
#define BOO_PATH /path/to/boost
which is actually useless. We need to have double quotes to cover them up.

BOOST = $ $ ( BOOST_PATH ) BOOST_STR = ' \ \ " $ $ { BOOST } \ \ " ' DEFINES += BOOST_PATH=\ " $ $ { BOOST_STR } \"

Again, eliminate the spaces :)

Hi koahnig its all working now but i get this warning:

<dump of C:\QT\Qt5.5.0\5.5\mingw492_32\qml>:1:24: Reading only version 1.1 parts.

<dump of C:\QT\Qt5.5.0\5.5\mingw492_32\qml>:10:5: Expected only Component and ModuleApi object definitions.

@mchinand finally its work , you can't imagine how much you help me
Thank you soooooooooo much :)

Thanks! It works!

@Jesse-James said:

What about within the Makefile? Is there a way that I could execute "qmake -makefile" from my Makefile? I think it's possible but I don't know how can I do it syntax-wise.

Yes, that is also possible.

I can't check myself right now, but something like that should work:

# Call qmake from custom makefile qmake MAKEFILE=myTempMakeFile myProFile.pro # Build the project make -j 8 # Remove the generated file (if you wish) rm myTempMakeFile

You may need to enclose MAKEFILE=myTempMakeFile in quotes, please test. Also, with that kind of stuff you need to be careful and test separately for each platform (especially Windows) as the syntax might be different there.