The build directory needs to be at the same level as the source directory.

kshegunov

@mrjj said in The build directory needs to be at the same level as the source directory.:

So its a new check of sorts?

Maybe only on windows. I always had that warning ...

jax1157

@kshegunov On Mac also. The check went away for a few years, but now it is back.

kshegunov

@jax1157 said in The build directory needs to be at the same level as the source directory.:

On Mac also.

I don't touch that stuff, sorry. I'm not rich enough to buy an overpriced PC.

The check went away for a few years, but now it is back.

The joke aside, I just might be remembering wrong, it happens too often I'm afraid.

mrjj

But why does it warn me?
It still works. And its really not on
same level as it's on a separate drive.

jax1157

@mrjj Yes agree - It does still work. It is mainly just annoying, because it is such a non-error. Nothing bad happens as a result.

ModelTech

Good to see that others have the same observation and I agree with option C in @jax1157 post as the preferred one over options A and B (and exactly the one I have as well). And indeed, despite the warning for the combination of versions mentioned, it works on Linux, Mac OS and Windows. I just don't like warnings too much if there is no real problem ;)

jax1157

sigh Looks like it is a QMake issue and they perhaps aren't planning to fix it!!

https://bugreports.qt.io/browse/QTCREATORBUG-16945

mrjj

Well I dont think the qmake guru should be the decision maker for Creator..
as its will soon become a pointless warning
and if some day you -do- have a project that suffer bad issues from location of build folder,
you will not think of this warning anymore.

Its a classic Cry wolf. Or will become.
https://en.wikipedia.org/wiki/The_Boy_Who_Cried_Wolf

Its not a big issue for me , but it's a bit annoying as i do like that projects have zero
warning.

So Ill go vote for them to make it possible to disable it.

Eeli K

Yes, this is a bit annoying, especially when it complains for this structure:

.../builds/
        project1_build_Release/
        project1_build_Debug/   etc.
.../projectsrc/
        project1.pro   etc.

This doesn't make any sense.

It should really warn about build directory being inside the source directory, and nothing else. Even then it should say "is recommended" or something like that, not "needs to be" because it doesn't need to be. And why it should be at the same level?

FirMoon

@mrjj
Put weight on this old answer for any future reference.

Yes, this is the place to be changed. I reset it (build directory) to my new source directory path, and everything works. See the link at:
https://blog.csdn.net/neuq_jtxw007/article/details/78774324