How to disable ""shadow build" ?
-
I believe this is re-post, but in case I am wrong ...
I have been caught it the "automatic shadow build" trap many times...
It seems to build on last edit and makes a mess.
I am asking
is there an option to permanently disable "automatic shadow build " ?
and to make sure I get a human reply and not AIif there is such option ,
then
where it is ?
....answer here
how to disable it ?
...answer hereThanks ,
any real help is greatly appreciated , but opinions are not... -
I believe this is re-post, but in case I am wrong ...
I have been caught it the "automatic shadow build" trap many times...
It seems to build on last edit and makes a mess.
I am asking
is there an option to permanently disable "automatic shadow build " ?
and to make sure I get a human reply and not AIif there is such option ,
then
where it is ?
....answer here
how to disable it ?
...answer hereThanks ,
any real help is greatly appreciated , but opinions are not...@AnneRanch Each Project has a checkbox to disable it. I'm not aware of a general option for all projects, and I would also advise against disabling it
-
I believe this is re-post, but in case I am wrong ...
I have been caught it the "automatic shadow build" trap many times...
It seems to build on last edit and makes a mess.
I am asking
is there an option to permanently disable "automatic shadow build " ?
and to make sure I get a human reply and not AIif there is such option ,
then
where it is ?
....answer here
how to disable it ?
...answer hereThanks ,
any real help is greatly appreciated , but opinions are not...@AnneRanch
For the benefits of posting know facts and or opinions.
"Shadow build" option is AUTOMATICALLY , by default , enabled per project , as such it defeats the purpose of having an option.AKA by default option should not be enabled - my opinion.
CASE CLOSED.
-
Actually, shadow builds are there to avoid messes. It avoids mixing debug and release builds, it avoids mixing different developer kits (combinations of compiler and Qt versions). If you don't separate those, you'll have a mess.
I personally don't use shadow builds either because they fill up my main directory quickly. And they are contrary to the way Visual Studio does it. I prefer having build folders as subfolders of my project directory and shadow builds don't allow me to do this.
-
Actually, shadow builds are there to avoid messes. It avoids mixing debug and release builds, it avoids mixing different developer kits (combinations of compiler and Qt versions). If you don't separate those, you'll have a mess.
I personally don't use shadow builds either because they fill up my main directory quickly. And they are contrary to the way Visual Studio does it. I prefer having build folders as subfolders of my project directory and shadow builds don't allow me to do this.
@SimonSchroeder said in How to disable ""shadow build" ?:
I prefer having build folders as subfolders of my project directory and shadow builds don't allow me to do this.
thats not true, you can specify the path of your shodow build and nothing is preventing you of using a subfolder of your source folder
-
@SimonSchroeder said in How to disable ""shadow build" ?:
I prefer having build folders as subfolders of my project directory and shadow builds don't allow me to do this.
thats not true, you can specify the path of your shodow build and nothing is preventing you of using a subfolder of your source folder
@J-Hilk said in How to disable ""shadow build" ?:
thats not true, you can specify the path of your shodow build and nothing is preventing you of using a subfolder of your source folder
Well, then this has changed. It still shows a warning when I do that. And I believe that this initially didn't work.
