[Qt-creator] 3 Compile issues (for projects) (4.12), 1 suggestion.

Jason H jhihn at gmx.com
Fri May 8 09:29:56 CEST 2020


> Sent: Thursday, May 07, 2020 at 7:08 PM
> From: "André Pönitz" <apoenitz at t-online.de>
> To: "Jason H" <jhihn at gmx.com>
> Cc: "qt-creator" <qt-creator at qt-project.org>
> Subject: Re: [Qt-creator] 3 Compile issues (for projects) (4.12), 1 suggestion.
>
> On Thu, May 07, 2020 at 06:21:32PM +0200, Jason H wrote:
> > 1. I have noticed for some time now, that QtC is sometimes compiling a file that
> > is not in the currently selected build configuration
> 
> The build configuration only sets parameters for your build system, Creator
> does not build anything directly, it's all done by the build system used.

I can see why you say that, but that could be the bug?
No ideas who the iOS file is being committed with the Android kit selected

> > -or- it is related to the next issue
> 
> > 2. The compile output area shows the compile error s for the file that is
> > currently visible. Well I should add that sometimes I have a split open so two
> > files are visible.
> 
> If the build errors do not contain enough information to identify a file
> e.g. because only a non-unique part of the file path is written it might
> be difficult to relate them to the file that caused the issue. Maybe what
> you are seeing is related to that.

My files are uniquely named. In the instant case, one is called platformshim_ios.cpp and the other is platform shim_and.cpp. Each is properly specd in the iOS {} or Android {} blocks in the pro. By all logic, the iOS file should not be compiled when the Android kit is selected.

> > 3. I had an iteration of a file where there was a typo in a #define and QtC's
> > checker just would just not let that error go after i corrected it.  Eventually
> > I closed the file and re-opened it and the above it worked as it should.
> > 
> > Is anyone else experiencing this?  This falls into one of those areas that occurs
> > often enough to be frustrating but easy to fix.
> 
> If it's easy to fix we should transfer this discussion to codereview.qt-project

Sorry I meant that the solution of closing and opening the file is easy.


More information about the Qt-creator mailing list