On Monday January 19 2015 15:41:13 Lawrence Velázquez wrote:
> What purpose does it serve to include target header paths while compiling?
Beats me too.
Well, not entirely. Qt has been moving away from a single monolithic build to
separate components, and indeed if you look at the Debian packagi
On Jan 19, 2015, at 6:01 AM, René J.V. Bertin wrote:
> As I mentioned before, Qt 5.4.0 has an issue building if Qt 5.3.2 is present
> in the destination: one of its components includes the target header path in
> the compiler header search path list, and then chokes when it includes a
> header