"dirty fiile " option ?

JonB

@AnneRanch
Qt doesn't decide what to (re)compile, it's the make it calls which does. As per the screenshot you showed. The question is why does that make seem to recompile before Run when the make from the Build has done.

when it fails - and QT complies again instead of running the output is valid but way it is too big

to post and immaterial

It is not immaterial. The issue is why/what it does. Right at the beginning of the output we probably need to know why it ever starts to compile anything, given that all should be already up to date.

J.Hilk

@AnneRanch change this setting on your own risk:

change the combobox "Build before deploying" from "Build the Whole Project" to "Do Not Build Anything"

and/or
uncheck "Always deploy project before running it"

Anonymous_Banned275

I have written this before JonB post.

So skip to the end for the latest .

I have changed my mind
after fighting with banana doing unexpected here is the real PROBLEM
(the way I see it )

WHEN SOURCE CODE HAS CHANGED / EDITED
and "Run" is executed this message is WRONG

"configuration " or whatever QT calls it HAS changed

the source files are "dirty"

banana QT is optioned to save updated / "dirty" files before "Run " and that is NOT happening.

ADDENDUM
IMHO we all need too take a look at the documentation ( RTFM ) and quit guessing what the banana coders are actually saying with various options.

In my opinion - the options should be in some order of precedence , hence
FIRST option is saying

BEFORE "build" OR "run" save files IF NEEDED

that again , in my opinion, should be before any other options

for example - it makes no sense to "deploy " if the above is not done,
nor run "debug"....

As far as who / which application is actually executing anything is immaterial - the result is wrong and I as a user
can only look for options. Especially when they are working at random, as far as I can tell.

I cannot change make , gcc, banana, QT ,,,,,

PS
At one point "debug" would come up with " source code in newer then ,,," so logically - the banana KNOWS it is working with outdated source - but runs anyway....

JonB

@AnneRanch
I think what @J-Hilk suggests is: uncheck that Always deploy project before running it. Does that make the Run button then not do an extra build before launching your application?

Anonymous_Banned275

...there got to be a pony in here somewhere....

Please - somebody take this seriously
Yesterday I did "build" and then "run" - the "run" took off IMMEDIATELY, no build / rebuild /etc
It just run.

Today - same project - keeps rebuilding after each "build" and also rebuilds again when "run" is selected.

This is not right.

Please do not sidetrack by blaming on version etc. - I have not changed verison for weeks,
As I pointed out - this has been a standard procedure since DOS 1,1

only files with changes shlud be rebuild,

REPLAY

DONE - removed "deploy" .option same s...t as before

Yesterday all was as expected , today "build" does build and "run" REPEATS the build....

I sure like to resolve this mess.
Can anybody come up with real , documented definitions of terms
options of "project" sub-menu>? ?

Then we can figure out what options controls it.
" run" builds project if necessary and runs the project (with green arrow (why?) ??)
"build" builds ONLY changed source...
"rebuild" rebuilds the entire project
"clean" deletes all executable project files
'deploy" ???????

Christian Ehrlicher

As I already said - your modification times of your files were mixed up. Your generated object files had a newer timestamp than your source files and therefore make thought there is nothing new and nothing needs to compile. Maybe the files only had an offset of some hours so today the object files were older than your sources and make needed to recompile your object files due to this.
This can happen when you e.g. modify your local time on the PC.

Anonymous_Banned275

@Christian-Ehrlicher You are trying to dilute the issue by making ridiculous assumptions.
So for your enjoyment

In a nutshell
If I run "build" and IMMEDIATELY run "run"
I do not expect "build" to be processed again.

THAT is a subject of a bug I have posted, hence no more speculations here are necessary.

In the meantime I am still looking for official documentation of options

run, build , rebuild, deploy

PS
As a bonus - can somebody identify the PURPOSE of green arrow next to "run" option ?

Christian Ehrlicher

@AnneRanch said in "dirty fiile " option ?:

You are trying to dilute the issue by making ridiculous assumptions.

No, I just know what make is doing under the hood and how it knows when to rebuild a source or when not. No QtCreator problem at all...

Anonymous_Banned275

Here are some definitions.

https://doc.qt.io/qtcreator/creator-glossary.html

...and here it one of interest

Run configuration Starts the application in the location where it was copied by the deploy configuration. By default, when you run a project, Qt Creator builds it, deploys it to the device specified in the selected kit, and runs it there. However, if you have not made any changes to the project since you last built and deployed it, Qt Creator simply runs it again.

The source of problem is in option

always deploy before run

and in
...Qt Creator builds it, deploys it to the device specified...

Qt Creator DOES NOT build when only "Run" is used .

I am not interested in verifying the "deploy" BUT apparently the "deploy" option does "build" which is NOT what the above definition of "Run" is saying - if its sequence means anything "...builds it, deploys it to the device specified in the selected kit, and runs.." then it MUST fail the way it does.

Mixing deploy / build / run the way this document does needs some serious explanation...
since the doc has no visible relations with actual settings of tool options

or just call this an unpleasant experience and move on ...

JKSH

@AnneRanch said in "dirty fiile " option ?:

In a nutshell
If I run "build" and IMMEDIATELY run "run"
I do not expect "build" to be processed again.

THAT is a subject of a bug I have posted

Set your computer's clock to 10 years into the future. That should stop "build" from being processed again if you run "build" and immediately run "run".

J.Hilk

@AnneRanch I think you're clicking the wrong buttons
see this picture:

the blue circled button will (I think) always rebuild, due to some debugger reasons
the red circled buttons should, when nothing was changed, do nothing. But I have seen exceptions to it, where some "compiling" was done, usually when I deploy to an other device, a phone for example.
the green circled button is the one you actually want to press, that one is the pure execute program button. That should do nothing but call the previously created executable.

As a bonus - can somebody identify the PURPOSE of green arrow next to "run" option ?

I know, I may out myself as an old person, but did you never own one of these ?

VCR player, tape player, Walkman, CD player, DVD player, blueray player, iPod?

That arrow is the common symbol for the "Play-Button" When you start something and it starts running/doing its thing...

JonB

This post is deleted!

Anonymous_Banned275

@J-Hilk

This is how I load the project

this is my opening / first screen of QT project

Then I right click on project and get submenu with "green arrow" " Run " option . ( I cannot screen shot that so you got to take my verbal description...) Select "Run" - highlighted and right click on it.

As of today - the project will run / execute irregardless if the source has been "build" or not.......

That does not agree with "Run (configuration ) " description.

BTW it should not matters which one of numerous "Run" buttons, arrows are used.

The green arrow in "application " works same , as of now wrong , way....

Back to the "run" definition
I am not going to argue QT document writers English - but how can you "deploy" before "build"?

JonB

@AnneRanch said in "dirty fiile " option ?:

but how can you "deploy" before "build"?

I think it's deploy after build (but before run):

Save files -> Build/compile -> Deploy (ensure some files are copied somewhere for runtime?) -> Run/Debug

Anonymous_Banned275

@JonB Agree , however this and documentation do not follow such sequence .

IMHO this is a grand mess - for example "save all files before build " "option" is stupid and illogical - it is saying
' go ahead and build irregardless of what changes were made. "
then you get "source is newer than.. " message.

Does anybody in QT company reads their stuff or do QA?

I would also add

After such sequence

Activating Build /compile AGAIN -> Project DOES NOT Build again and gives correct message
( I did nothing because...) - that worked at some point as documented in this discussion. .

I am still waiting on response on bug I posted.

JonB

@AnneRanch said in "dirty fiile " option ?:

IMHO this is a grand mess - for example "save all files before build " "option" is stupid and illogical - it is saying
' go ahead and build irregardless of what changes were made. "
then you get "source is newer than.. " message.

No. I am quite sure the full title of that checkbox is meant to be/should be read as:

"Save all files which you are presently editing, DO have some changes, and have not yet been saved to disk before build"

It will just be that standard stuff: since it's about to invoke the external compiler you are just confirming you want to to save any pending changes you might have made in the editor so that the compiler will see them without you actually having to press buttons to save them yourself. You could verify that by looking at your source files' timestamps/date modifieds, I think/hope you will only see those which you changed updated, not unchanged source files.

Activating Build /compile AGAIN -> Project DOES NOT Build again and gives correct message

I was going to ask that. I think you are saying in your situation:

If you Build and then immediately Build again it does not recompile stuff.
If you Build and then Run or Debug it does recompile stuff.

I don't know why it is doing that, I don't think it should.

I am still waiting on response on bug I posted.

Did you post a link reference here to the bug you have raised on https://bugreports.qt.io/ ?

Anonymous_Banned275

@JonB said in "dirty fiile " option ?:

@AnneRanch said in "dirty fiile " option ?:

IMHO this is a grand mess - for example "save all files before build " "option" is stupid and illogical - it is saying
' go ahead and build irregardless of what changes were made. "
then you get "source is newer than.. " message.

No. I am quite sure the full title of that checkbox is meant to be/should be read as:

"Save all files which you are presently editing, DO have some changes, and have not yet been saved to disk before build"

It will just be that standard stuff: since it's about to invoke the external compiler you are just confirming you want to to save any pending changes you might have made in the editor so that the compiler will see them without you actually having to press buttons to save them yourself. You could verify that by looking at your source files' timestamps/date modifieds, I think/hope you will only see those which you changed updated, not unchanged source files.

Activating Build /compile AGAIN -> Project DOES NOT Build again and gives correct message

I was going to ask that. I think you are saying in your situation:

If you Build and then immediately Build again it does not recompile stuff.

If you Build and then Run or Debug it does recompile stuff.

If you Build and then immediately Build again it does not recompile stuff.

From my first post - NO it does not work that way.

When I do "Build" and immediately do "Build" again - IT BUILDS!
That is wrong ....

When I do "Build" and immediately do "Run" - IT BUILDS
again and then runs.
That is also wrong. !

If I REMOVE "deploy before running " option then
when I do "Build" and IMMEDIATELY do "Run " it runs.

That is correct.

I don't know why it is doing that, I don't think it should.

I am still waiting on response on bug I posted.

Did you post a link reference here to the bug you have raised on https://bugreports.qt.io/ ?

QTCREATORBUG-27815

Anonymous_Banned275

One more issue and I strongly feel it belongs in this thread.

First - success - AFTER configuring the "shadow build directory " SEPARATE from "project directory" all "build" "clear" "rebuild" and "run" works as expected .

As a "bonus" changing "build " or "run" actually does "build " or "run" without clicking anything more .

What is left are relation between

"shadow directory "
"working directory"
"executable directory "
"project directory "

There are reasonable definitions of the above directories , but their interaction is not that clear.

I can select both shadow and working directories , however "executable " is "stuck" on value I do not recall selecting.

Also missing is "definition " of
"project directory " .

Anonymous_Banned275

OK, I am getting nowhere fast .

**The latest anomaly - when I change anything in QTDesigner QTCreator has no knowledge about it .
It does not matter what "configuration" I implement - "Build", "run qmake", "Clear /Rebuild" and "Run".

IT USED TO WORK.**

I am really looking for CLEAR instructions HOW to "configure" QT to build and run and keep QTCreator updated with (latest )
changes in QTDesigner.

Is there anybody in this group willing to discuss and come with old fashioned flow chart / sequence of directories to configure ?

From sad experience - these directories options DEPEND on each other AT RANDOM fashion
there needs to be a clear repeatable path in configuring these options.

The documentation DOES NOT provide clear way to set these options so they work in harmony and not
in random fashion.

Here is a start:

Projects directory ?? (plural )

"current directory " ???
or
selected (project) (singular) directory ??? (x.pro ???)

What is “project directory “ SINGULAR

Shadow build
enabled and selected - must be in same level as project directory
or just disabled ??

The doc leads one to believe that only ONE project is build -
either in project directory or in shadow directory.
Which one is actually "run" is not told - that should be obvious
(or part of compile output ) but
so far nothing in banana is obvious.

Executable ?? what ??
electable does what if NOT implemented ??

working directory ??
electable does what when NOT selected ??

Anonymous_Banned275

I feel like beating a dread horse ... the more I get into this mess the worse it gets .

Here are my latest observations

When Qt finally starts I get a pop-up in lower right corner with a ton of progress bars and changing small prints of their descriptions
when this pop-up goes away I can right click on highlighted project and select "Run"...
There are no other visible changes to indicate Qt is ready to run the project...
AFTER I am done editing I can "Ctrl +B" - build - and I get the "pop-up" going again as described in #1
(Anybody care to tell me what is the official name of this pop-up and WHERE it is described ?)
While (!) the "pop_up" is RUNNING I can "Ctrl+R" and my project will eventually run...
I like to combine these Ctrl shortcuts , but so far no luck - there are too many superfluous shortcut conflicting with my idea of " build and run " shortcut.
Anybody have a software to give a list of UNUSED shortcuts in Qt ? ( OK i'll ask Mrs Google)