I would like to ask for some expert tutorial or some hints for using
qmake with huge projects.
What is huge? Our complete package consists of 50 applications build
based on 100 libraries (organized in modules and units). On Windows, we
use a Visual Studio solution file containing 250
On Fri, Apr 19, 2013 at 12:18 PM, Rainer Wiesenfarth
rainer_wiesenfa...@trimble.com wrote:
I would like to ask for some expert tutorial or some hints for using
qmake with huge projects.
What is huge? Our complete package consists of 50 applications build
based on 100 libraries (organized in
Hi,
On Fri, Apr 19, 2013 at 10:35 AM, Mandeep Sandhu
mandeepsandhu@gmail.com wrote:
On Fri, Apr 19, 2013 at 12:18 PM, Rainer Wiesenfarth
rainer_wiesenfa...@trimble.com wrote:
I would like to ask for some expert tutorial or some hints for using
qmake with huge projects.
What is
Am 19.04.2013 10:35, schrieb Mandeep Sandhu:
[...]
The single application's pro file should have all the libs it depends
on, listed in the depends variable.
Thanks for your answer, I will take a look at depends - I did not yet
read in depth about its meaning and impact.
Best Regards / Mit
Am 19.04.2013 11:25, schrieb Bo Thorsen:
Sounds to me like you want to switch to cmake instead. That has a lot
better support for dependencies between subprojects than qmake. And for
a project of this size, I would expect you have some fancy build stuff
in there as well, and qmake is usually too
qmake takes care of this (I think), i.e it'll find out the number of cores
and supply the relevant number to make's -j option.
No, qmake does not take care of this as qmake is not a buildsystem itself
(rather a buildsystem generator, it generates Makefiles, VS files etc.).
But of course a
Den 19-04-2013 12:29, Rainer Wiesenfarth skrev:
Am 19.04.2013 11:25, schrieb Bo Thorsen:
Sounds to me like you want to switch to cmake instead. That has a lot
better support for dependencies between subprojects than qmake. And for
a project of this size, I would expect you have some fancy
On Friday, 19 April 2013 12:29:04 CEST, Rainer Wiesenfarth wrote:
well, I know about cmake, but was going for something less cryptic... :-)
One of my biggest disappointments with qmake was that it just did not set up
proper dependencies between the static libs I build and the targets which use
Den 19-04-2013 13:36, Jan Kundrát skrev:
On Friday, 19 April 2013 12:29:04 CEST, Rainer Wiesenfarth wrote:
well, I know about cmake, but was going for something less cryptic... :-)
One of my biggest disappointments with qmake was that it just did not set up
proper dependencies between the
Am 19.04.2013 13:36, schrieb Bo Thorsen:
On the bright side: Once you have a good cmake build in place, you will
have the visual studio build done with the same system as Linux. Having
two different build systems is *not* a good idea.
I know, but we will definitely have two build systems -
Hi Rainer,
as other members already stated out qmake has some limits - but:
These can be hacked ;-)
We (our company) spent much time to discover different build systems and
approaches -
where CMake was the most complicated and most work intensive solution.
So we decided to use the long term and
QMake and CMake both generate what your final build environment need, whether
it is Makefiles for GNUmake, nmake, or VS projects.
So you can have one project definition set that generates for all build
environments. I highly recommend it.
I'd further advise that you probably want to use CMake
I've used QMake in two large cross-platform projects, one of which wasn't
even a Qt application. I did look at other options including CMake and
Premake 4 but decided to stick with QMake.
Here are my thoughts:
- The documentation is poor and in some case misleading and wrong. Google
On Fri, Apr 19, 2013 at 03:36:21PM +0100, Danny Price wrote:
I've used QMake in two large cross-platform projects, one of which wasn't even
a Qt application. I did look at other options including CMake and Premake 4
but
decided to stick with QMake.
Here are my thoughts:
[...]
-
On 19 Apr 2013, at 20:49, André Pönitz
andre.poen...@mathematik.tu-chemnitz.de wrote:
On Fri, Apr 19, 2013 at 03:36:21PM +0100, Danny Price wrote:
I've used QMake in two large cross-platform projects, one of which wasn't
even
a Qt application. I did look at other options including CMake
Hi,
indeed - as one of the QMake advanced users (or hackers ;-) ) I agree that
QMake has an unsufficient
documentation for usage in more complex projects - see
https://bugreports.qt-project.org/browse/QTBUG-28428.
Without having to edit .pro and .pri files outside the QtCreator and to use many
Hi,
apropos:
I could supply some more complex examples for .pro and .pri - including some
basic
utilities and environment stuff realized inside qmake files - if it helps
ciao,
Chris
On 20. April 2013 at 00:20 Christian Dähn da...@asinteg.de wrote:
Hi,
indeed - as one of the QMake
Hi Everybody,
It seems this is not possible, -no-webkit is marked as Windows only in the
configure options docs, why is that? If Qt was smart enough to link to the
system webkit on Mac, it might make sense, but that doesn't happen.
I would like to distribute my app via the Apple app store
18 matches
Mail list logo
