Empty unused build folders ...

[ademmler]

Hi there, in my *.pro file I use

CONFIG(debug, debug|release) {
    DESTDIR      = $$PWD/build/debug/
} else {
    DESTDIR      = $$PWD/build/release/
}

On Mac OS X I get only the two expected folders:

"myproject/build/debug"
"myproject/build/release"

On Windows I get additional empty folders (4 in total):

"myproject/debug"
"myproject/release"

How can I prevent this?

[SGaist]

Hi,

IIRC, that's because of VS and you can't change that.

In any case, I would suggest to avoid hard coding the build parts in your sources. You should rather take advantage of out of source builds.

[ademmler]

@SGaist thx for response.

VS = Visual Studio you mean - right?

"In any case, I would suggest to avoid hard coding the build parts in your sources. You should rather take advantage of out of source builds."

This part I have not understood - can you explain a bit more?

[SGaist]

@ademmler said in Empty unused build folders ...:

DESTDIR = $$PWD/build/debug/

This points DESTDIR to be in your sources. You should avoid that. Keeping the source clean from build artefacts is good habit.

[ademmler]

@SGaist I see - I got this advice from an "older qt developer" to do the opposite :-)
By the way - what are the shadow builds for -I ran into problems, when I keep those activated.

[SGaist]

Shadow builds are out of source builds so if you start forcing stuff within your sources then you'll have trouble.

You can still control some stuff by using the "OUT_PWD" variable which should point to the build build tree. That can be useful for example when you use a SUBDIRS project and would like to have all the build libraries in on folder that you can easily access from the other projects.

[SGaist]

@ademmler said in Empty unused build folders ...:

"older qt developer"

Out of curiosity, how old would that be ? :-)

[ademmler]

@SGaist He does Qt since many years ... but he is in many aspects not up to date ;-)