Hi,
I must have mentioned already that I am maintaining a project that provides
backported and slightly customised versions of the Cocoa QPA and the Macintosh
style (called Aqua to avoid hiding the official version). The stable branch
currently has these plugins from the qtbase 5.9 branch and w
Hello list:
I have an application.
I would like to rearchitect it were 90% is in a shared library.
I would use that lib to link a main application.
I would like to create a single .pro file that can be
used to create both the library and main app.
I do not want to create the lib and app in separa
2018-02-08 13:56 GMT+01:00 william.croc...@analog.com <
william.croc...@analog.com>:
> I have an application.
> I would like to rearchitect it were 90% is in a shared library.
> I would use that lib to link a main application.
> I would like to create a single .pro file that can be
> used to creat
Hi all,
It *is* possible with QMake, if you accept to have two additional
pro files: lib.pro for the library and the app.pro for the program.
The main pro file then looks like this:
TEMPLATE = subdirs
SUBDIRS += \
lib \
app
lib.file = lib.pro
app.file = app.pro
The lib.file a
It sadly seems that I found no interest in the Interest groups as
regarding the VNC back-end.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
It sadly seems that I found no interest in the Interest groups as
regarding the VNC back-end.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
On 02/08/2018 08:34 AM, André Hartmann wrote:
Hi all,
My goal is to keep all files in the same directory and all .pro logic in the
same file.
QMake should be ashamed of itself.
I will read up on Qbs.
Thank you everyone for responding.
Bill
(...and for the record, I am who I appear to be.)
On Thursday, 8 February 2018 04:56:02 PST william.croc...@analog.com wrote:
> I would like to create a single .pro file that can be
> used to create both the library and main app.
Get rid of this requirement and then you can accomplish what you want.
--
Thiago Macieira - thiago.macieira (AT) int
2018-02-08 16:47 GMT+01:00 william.croc...@analog.com <
william.croc...@analog.com>:
>
> My goal is to keep all files in the same directory and all .pro logic in
> the same file.
> QMake should be ashamed of itself.
>
Why? It is a design decision made by the people who made qmake to have 1
.pro f
Announcing GammaRay 2.9.0
Highlights of this Release:
=
* Improve Qt Quick Controls 2 tracer coloring.
* Fix issues with QSG diagnostic render modes in combination with QQuickWidget.
* Improve input validation in the connect dialog.
* Fix Qt Quick remote view on targets wit
My goal is to keep all files in the same directory and all .pro logic in the
same file.
QMake should be ashamed of itself.
Why? It is a design decision made by the people who made qmake to have 1 .pro
file per major target.
The most obvious evidence is the `TEMPLATE` variable in p
On a more general note: here's a standalone version of the oxygen-demo utility.
Very handy when you work on widget styles (or platform [theme] plugins), I find.
R.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/li
> On a more general note: here's a standalone version of the oxygen-demo
Oops, it's here: github.com/RJVB/qstyle-demo
Apologies.
R.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
2018-02-08 19:22 GMT+01:00 william.croc...@analog.com <
william.croc...@analog.com>:
>
> If I create a separate .pro file for lib and main,
> I would then have to create yet a third file
> to hold the common lines for inclusion in those first
> two. That is not moving in the right direction.
>
Ma
14 matches
Mail list logo
