On Monday 04 August 2014 08:57:25 Sumedha Widyadharma wrote:
> See: mkspecs/features/qt_example_installs.prf
>
> > You can assign any value to any variable you want in qmake. Whether you
> > make use of the variable or not, it's up to you.
>
> This variable is used internally.
You mean "external
On Fri, Aug 01, 2014 at 04:45:16PM +0200, Sumedha Widyadharma wrote:
> It is silently dropped, you have to enable CONFIG+=check_examples to
> get a notice about this. Why is that?
>
> Shouldn't it always warn the user?
>
there are some false positives which i found non-trivial to avoid
cleanly, s
Morning,
EXAMPLE_FILES contains a list of additional example files for a project.
The files referenced in the variable will be installed by qmake to the
appropriate examples destination.
See: mkspecs/features/qt_example_installs.prf
On 08/02/2014 06:19 PM, Thiago Macieira wrote:
> On Friday 01
On Friday 01 August 2014 16:45:16 Sumedha Widyadharma wrote:
> Hi,
>
> This seems to be forbidden in a .pro file:
>
> EXAMPLE_FILES += ../some/file
>
> what is the rationale behind not allowing this?
Why is it forbidden?
> It is silently dropped, you have to enable CONFIG+=check_examples to ge
Hi,
This seems to be forbidden in a .pro file:
EXAMPLE_FILES += ../some/file
what is the rationale behind not allowing this?
It is silently dropped, you have to enable CONFIG+=check_examples to get
a notice about this. Why is that?
Shouldn't it always warn the user?
Regards,
Sumedha Widyadha
