Well, given the two choices;
"This is a custom makefile": in this case if none of the other settings in C::B takes effect, then qmake will not be run and no makefile will be generated.
Not using "This is a custom makefile": in this case qmake is run and the Makefile is created and I get the above listed problem.
So, I've tried something else:
Change the qmake commands to
qmake -project
qmake "TARGET=default"
for ease of target use.
Unset the use custom makefile setting and build, I get the makefile built and the compile errors as noted previously. Then I set the custom makefile setting and build, everything gets built, but the program doesn't actually run. Then, when I choose Run again, C::B tells me the project hasn't been built and asks if I want to build it. I say yes and it tells me that there is nothing to be done for default (the target). I check, and yes, the app has been built, and I can run it from the terminal, but I can't run it from within C::B.
So, the problem here seems to be that I need a way to invoke qmake from within C::B in order to generate a the custom Makefile -- but, if I use a custom Makefile, then the pre-build commands don't get executed...
Also, if I don't use a custom makefile, am I to understand the C::B will generate one? Where is it? I certainly don't see it, the only one that is there is the one generated by qmake.
Mage2k