How do I build project in current directory on Windows?

[Coolname007]

Oh great...
Now to add to my list of problems, I'm now seeing that the header file its complaining about is not even showing up in the Projects file tree pane, or whatever you call it. Even though the path to the file is correct, and the file exists, and I've also tried removing it from the project, and then adding it again through right-click to project->select "Add Existing Files" and then selected the trouble file again, but still its not showing up in the tree view. And of course, I'm still getting the "no rule to make target" error again...

So I don't know what the hell is the problem.

EDIT: Oh even better. Now the forum seems to have copied my original post and added my new post's text above to the copy of the original post after the text "Added after X amount of minutes", and so I tried to edit my second post, and removed the original post's content from that, and tried to save it so that it would only have the new post's content, but that only fucked up my original post to contain the same content as my second post which I tried to save, and deleted my second post. So now I'm really fucked...

[wysota]

Don't worry, here is your original post

Hello.
I'm wondering how to build project in current directory of .pro file, instead of "debug" or "release" subfolder.
The reason I need to do this is because when I tried building my project, it complained about "No rule to make target 'blah blah blah' needed by /debug/C_html4_attributes.o'. Stop.".
So I went and looked in my Makefile.debug file and discovered the reason for the problem: its looking for the included header files in parent directories of the "debug" subfolder, instead of parent directories of the current directory, meaning qmake did not evidently generate the right paths for the makefile, and adjust the header include paths to account for the debug subfolder, but instead just copied them as it is in the .pro file, thus creating the problem I'm having only on Windows (the same project builds just fine on another OS - Ubuntu - on the same computer, obviously because in Linux, it does not build the executable in a subfolder, but builds it in the same directory as the .pro file).

Anyone have any solution for this problem??

Thanks in advance..

---

Added after 49 minutes:

Oh great...
Now to add to my list of problems, I'm now seeing that the header file its complaining about is not even showing up in the Projects file tree pane, or whatever you call it. Even though the path to the file is correct, and the file exists, and I've also tried removing it from the project, and then adding it again through right-click to project->select "Add Existing Files" and then selected the trouble file again, but still its not showing up in the tree view. And of course, I'm still getting the "no rule to make target" error again...

So I don't know what the hell is the problem.

[Coolname007]

Thanks wysota.

UPDATE on the issue:

It turns out I was wrong. The problem wasn't that it was looking at the relative path from the perspective of the "debug" folder (I thought that because in the Makefile.debug it showed for the C_html4_attributes.o object file the paths to the header files which the C_html4_attributes.o needed in order to compile, one of which was the target file it was complaining about, i.e. S_html_attr_value.h, and I was thinking that the paths were being used by the .o file, but then I realized that no...the paths are being used by the make program which is looking at the relative paths from the perspective of the current directory of the MAKEFILE.debug file, and so there is no problem there). However, I did track down the issue anyway and fixed it. It turned out I was using too many subfolders in the project, and so two many characters were in the filepath I guess, which Windows doesn't like, so that's why it was reporting that problem: evidently either qmake or maybe mingw's make program wasn't able to access the file due to the extremely long filepath, and thus wasn't able to generate a rule or maybe execute a rule on that file, thus creating the issue.
So once I removed some umpteen "modules" subfolders from the project, it compiled and ran without any problems.

So I am happy to say that this problem is resolved.