The build directory needs to be at the same level as the source directory.
-
@jax1157 said in The build directory needs to be at the same level as the source directory.:
Yes - That structure that you have shown there is exactly what we are trying to avoid.
If you ask me that's the structure you should be striving for, all builds having all the necessary isolation from one another and being out of the source tree, but that's just my opinion. I don't think you can have "Shadow building" enabled in Creator and have the build folder on a level different from the source.
-
You definitely used to be able to do it - The warning is only since 4.1.0. I do remember it doing it in 2011 (now that you mention it), but they fixed that up pretty quickly.
Just to explain re builds:
A shadow looks like this with no builds:
- Shadow
- Toplevel1.pro
- Source1
- Source2
The choices are:
Option A
- Shadow
- Toplevel1.pro
- Source1
- Source2
- Build1
- Build2
Ugly - Top level of the shadow now has a heap of build directories (1 per config), all of which have to be ignored, and mixed in with the source. Also - This is what Qt Creator seems to want by default.
Option B
- Build 1
- Build 2
- Shadow
- Toplevel1.pro
- Source1
- Source2
Definitely not! If you have >1 shadow (from different branches of the same source), then the build directories conflict.
Option C
- Shadow
- Toplevel1.pro
- Source1
- Source2
- Build
- Build1
- Build2
What I want. Most common structure I have seen. Can clean source tree completely by removing "build" directory only. No conflicts with other shadows. Used to work - Now doesn't.
- Shadow
-
Im also starting see these after upgrade.
I did not change project layout and it do not show in version before 4.1.0
So its a new check of sorts?
I have all build folders on ramdrive. since day one. never saw this message before.
-
@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 ...
-
@kshegunov On Mac also. The check went away for a few years, but now it is back.
-
@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.
-
But why does it warn me?
It still works. And its really not on
same level as it's on a separate drive. -
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 ;)
-
sigh Looks like it is a QMake issue and they perhaps aren't planning to fix it!!
-
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_WolfIts 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.
-
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?
-
@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
