Console Applications
-
@tomy
Well do you see .o file ? Maybe there is a build folder one level up?
If not, then show the log (text) you get from running mingw32-make (step)
Maybe there is compile or link error as that would do that no .exe is created.Ah, sorry. Its in the release folder
Oops sorry I forget that in windows things like Release/ and Debug/ folders. :)
My L-GPL'd C++ Logger github.com/ambershark-mike/sharklog
-
Oops sorry I forget that in windows things like Release/ and Debug/ folders. :)
@ambershark
Well i had to follow the sample and see. Was not sure what would really happen :) -
@ambershark
Well i had to follow the sample and see. Was not sure what would really happen :)@mrjj Lol. I'm glad it actually worked since I just typed that out without testing anything. And I don't use windows much so I could easily have messed it up. :)
-
Look, I did these:
Creating a C++ file named "main" with a simple code in it, in the "test" folder.
Then, found and ran all three commands (qmake -project, qmake, mingw32-make).
And the result as shown above (with no ".exe" file in the "test" folder.
I CMD:
-
Look, I did these:
Creating a C++ file named "main" with a simple code in it, in the "test" folder.
Then, found and ran all three commands (qmake -project, qmake, mingw32-make).
And the result as shown above (with no ".exe" file in the "test" folder.
I CMD:
-
Look, I did these:
Creating a C++ file named "main" with a simple code in it, in the "test" folder.
Then, found and ran all three commands (qmake -project, qmake, mingw32-make).
And the result as shown above (with no ".exe" file in the "test" folder.
I CMD:
-
Hi
An alternative to fiddling with path is to run the
c:\Qt\5.8\mingw53_32\bin\qtenv2.bat
in the cmd before trying to compile.Hi
An alternative to fiddling with path is to run the
c:\Qt\5.8\mingw53_32\bin\qtenv2.bat
in the cmd before trying to compile.Hi,
"The system cannot find the path specified."
Anyway, it's not that important and we can leave it out because it's not my purpose to be familiar with running files from CMd, now. Maybe when needed.
(I liked to test that simple example this way but, the testing may not be so easy) Thanks. -
Hi
An alternative to fiddling with path is to run the
c:\Qt\5.8\mingw53_32\bin\qtenv2.bat
in the cmd before trying to compile.Hi,
"The system cannot find the path specified."
Anyway, it's not that important and we can leave it out because it's not my purpose to be familiar with running files from CMd, now. Maybe when needed.
(I liked to test that simple example this way but, the testing may not be so easy) Thanks. -
Yes, I did it and I think the system is set now and ready for the next tests. You can look at this:
"text.exe" exists but nothing is shown after test.exe in CMD.Update:
After re-opening the CMD and testing the .exe:
@tomy
what code you write in test? -
Yes, I did it and I think the system is set now and ready for the next tests. You can look at this:
"text.exe" exists but nothing is shown after test.exe in CMD.Update:
After re-opening the CMD and testing the .exe:
-
Hi
An alternative to fiddling with path is to run the
c:\Qt\5.8\mingw53_32\bin\qtenv2.bat
in the cmd before trying to compile.Hi,
"The system cannot find the path specified."
Anyway, it's not that important and we can leave it out because it's not my purpose to be familiar with running files from CMd, now. Maybe when needed.
(I liked to test that simple example this way but, the testing may not be so easy) Thanks.@tomy said in Console Applications:
"The system cannot find the path specified."
Well you need to use the correct path for your installation.
It sets the correct path for tools but that you can also do in other ways. -
Yes, I did it and I think the system is set now and ready for the next tests. You can look at this:
"text.exe" exists but nothing is shown after test.exe in CMD.Update:
After re-opening the CMD and testing the .exe:
@tomy
You need to provide the DLLs it wants from the CORRECT compiler folder under c:\Qt
so you end up with (maybe more DLLs)
Please read
http://www.tripleboot.org/?p=138 -
@tomy
You need to provide the DLLs it wants from the CORRECT compiler folder under c:\Qt
so you end up with (maybe more DLLs)
Please read
http://www.tripleboot.org/?p=138 -
You need to provide the DLLs it wants from the CORRECT compiler folder under c:\Qt
so you end up with (maybe more DLLs)I added them from the folder: C:\Qt\Qt5.8.0\5.8\mingw53_32
No reaction.@tomy
Did you read the link ?
Anyway, it might need extra dlls :)
You can try the tool
http://doc.qt.io/qt-5/windows-deployment.htmlor use
http://www.dependencywalker.com/
To check the dlls.Anyway, to make it run, that release folder must be an deployment folder so keep reading docs and it will work :)
-
At the beginning there were only four simple CLI commands to get the result on our contraction, but now I see after doing more than 4x commands I haven't the file run, and still need to go on!
Why should we bother themselves this way! In the Qt Creator or Visual Studio (for console apps) we can get the result in 10x faster than this CLI method.CLI may be faster in some cases, but not in this one, at least!
Thank you all. Let's don't continue the topic. Thanks again. -
At the beginning there were only four simple CLI commands to get the result on our contraction, but now I see after doing more than 4x commands I haven't the file run, and still need to go on!
Why should we bother themselves this way! In the Qt Creator or Visual Studio (for console apps) we can get the result in 10x faster than this CLI method.CLI may be faster in some cases, but not in this one, at least!
Thank you all. Let's don't continue the topic. Thanks again.@tomy
well being experienced means you know for each job what is the right tool.
Besides using GUI or CLI is 2 sides of same coin. If you look in
Creator/VS you can see the command line it uses to get the job done.So if i need CLI action i will visually create and edit files and then simply steal the CLI line to build it.
That way i can use CLI when it suits :)
Its not fair to dismiss CLI as GUI would be nothing without it.
GUI was invented to make life easier for those of us that feels CLI is just too much typing but i work with ppl that can create something 10X faster using CLI. Building libs and dependencies. They like CLI for the direct
power user control it gives. If its not for your liking ( or mine ;) then its not the tools fault in my opinion.The reason it just dont work for you is that the environment is not setup and u are used to the IDE setting it up before running exe. The qtenv2.bat was part of that automation etc. So power user will bother to use CLI as its
efficient and there is noi layer in between (the IDE) so they prefer CLI and some kinky editor :)
