Hi Rainer,
I suggest you to review QmkBld project:
https://code.google.com/p/qmkbld/
https://code.google.com/p/qmkbld/wiki/QmkBld
It might fulfill some of requirements.
Kind regards,
Semih Cemiloglu
semih (at) cemiloglu.org
On Fri, Apr 19, 2013 at 4:48 PM, Rainer Wiesenfarth <
rainer_wiesen
Nothing against qmake, but IHMO it definitely pays off to learn cmake.
Especially the cpack addition makes it worthwhile. Easy packaging for
Windows using the NSIS installer, easy deb and rpm packages for Linux,
and packages for OSX. This feature alone makes cmake far superior to
qmake.
Guido
> T
Thanks a lot for all your hints and links! I get the feeling that I can
easily spend a week learning the secrets of qmake. :-)
My first impression is that qmake probably will suit fine, without
introducing the complexity of cmake. But it definitely will be the
second build system (for non-Wind
Den 22-04-2013 19:22, Konrad Rosenbaum skrev:
> On Friday 19 April 2013 13:36:36 Bo Thorsen wrote:
>> Den 19-04-2013 12:29, Rainer Wiesenfarth skrev:
>>> well, I know about cmake, but was going for something less cryptic... :-)
>>>
>>> We have some fancy build stuff (f2c, versioning, ...), but I wa
On Friday 19 April 2013 13:36:36 Bo Thorsen wrote:
> Den 19-04-2013 12:29, Rainer Wiesenfarth skrev:
> > well, I know about cmake, but was going for something less cryptic... :-)
> >
> > We have some fancy build stuff (f2c, versioning, ...), but I was hoping
> > to get it done with qmake, _because
senfarth
>To:
>Cc: interest@qt-project.org
>Sent: Friday, April 19, 2013 8:33 AM
>Subject: Re: [Interest] qmake: questions regarding huge projects
>
>
>Am 19.04.2013 13:36, schrieb Bo Thorsen:
>> On the bright side: Once you have a good cmake build in place, you will
>
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 an
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 - unle
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 t
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 fanc
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
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
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 / Mi
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.
>
Hi Rainer,
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 simple for it.
Bo.
Den 19-
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 (or
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 proje
17 matches
Mail list logo
