Yet it seems we both agree that 2 complex classes (let's say QString and
QObject)
are often declared in different files and that a file can contain more than one
class declaration, in particular if they are helper classes.
Agreed.
My final solution looks like this:
build_lib {
# Build
2018-02-09 14:40 GMT+01:00 william.croc...@analog.com <
william.croc...@analog.com>:
>
>
>> Think about C++ classes and files. If you have 3 classes like A, B and C,
>> it is
>> common practice
>> to have them defined in 3 header files in particular if they are complex
>> classes, even if both B
Think about C++ classes and files. If you have 3 classes like A, B and C, it is
common practice
to have them defined in 3 header files in particular if they are complex
classes, even if both B and C inherits from A.
And hardly anyone would try to put the 3 of them in a single header file, even
On Thursday, 8 February 2018 13:22:12 CET william.croc...@analog.com wrote:
> 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.
>
> The bad
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.
>
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
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
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)
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.)
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
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
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
12 matches
Mail list logo
