Trolltech Home | Qt-interest Home | Recent Threads | All Threads | Author | Date
All threads index page 5

Qt-interest Archive, August 2006
SUBDIRS + "make release"

Pages: Prev | 1 | 2 | Next

Message 1 in thread

Hi,

I have a top-level .pro using the SUBDIRS template. All my other .pro 
use debug_and_release. I want to be able to to "make release" from the 
top-level directory. Currently, I get

make: Nothing to be done for "release".

What can I do?

Thanks

--
 [ signature omitted ] 

Message 2 in thread

On 24.08.06 14:22:32, Simon Perreault wrote:
> I have a top-level .pro using the SUBDIRS template. All my other .pro use 
> debug_and_release. I want to be able to to "make release" from the top-level 
> directory. Currently, I get
> 
> make: Nothing to be done for "release".
> 
> What can I do?

I haven't tested this, but did you try adding CONFIG +=
debug_and_release in the top-level project file?

Andreas

-- 
 [ signature omitted ] 

Message 3 in thread

Andreas Pakulat wrote:
> I haven't tested this, but did you try adding CONFIG +=
> debug_and_release in the top-level project file?

Yes I did, and it did not seem to make any difference.

--
 [ signature omitted ] 

Message 4 in thread

On 24.08.06 15:16:51, Simon Perreault wrote:
> Andreas Pakulat wrote:
> >I haven't tested this, but did you try adding CONFIG +=
> >debug_and_release in the top-level project file?
> 
> Yes I did, and it did not seem to make any difference.

I think you should write a wishlist report to TT.

Andreas

-- 
 [ signature omitted ] 

Message 5 in thread

Andreas Pakulat <apaku@xxxxxx> wrote on 08/24/2006 02:35:25 PM:

# On 24.08.06 15:16:51, Simon Perreault wrote:
# > Andreas Pakulat wrote:
# > >I haven't tested this, but did you try adding CONFIG +=
# > >debug_and_release in the top-level project file?
# >
# > Yes I did, and it did not seem to make any difference.
#
# I think you should write a wishlist report to TT.

I'll mention that I did file a bug report on this at some point,
and I got pointed here:
http://www.trolltech.com/developer/knowledgebase/693

I don't think this is really a solution, though.

--
 [ signature omitted ] 

Message 6 in thread

On 29.08.06 16:00:08, Gordon.Schumacher@xxxxxxxxxxx wrote:
> Andreas Pakulat <apaku@xxxxxx> wrote on 08/24/2006 02:35:25 PM:
> 
> # On 24.08.06 15:16:51, Simon Perreault wrote:
> # > Andreas Pakulat wrote:
> # > >I haven't tested this, but did you try adding CONFIG +=
> # > >debug_and_release in the top-level project file?
> # >
> # > Yes I did, and it did not seem to make any difference.
> #
> # I think you should write a wishlist report to TT.
> 
> I'll mention that I did file a bug report on this at some point,
> and I got pointed here:
> http://www.trolltech.com/developer/knowledgebase/693
> 
> I don't think this is really a solution, though.

That isn't even the same problem. The OP's problem is that the Makefile
generated by qmake in the top-level dir doesn't have a release or debug
target. However the non-subdirs Makefile's have these. The OP just wants
to issue make release in his top-level dir instead of walking through
all subdirs...

Andreas

-- 
 [ signature omitted ] 

Message 7 in thread


Andreas Pakulat wrote:
> 
> That isn't even the same problem. The OP's problem is that the Makefile
> generated by qmake in the top-level dir doesn't have a release or debug
> target. However the non-subdirs Makefile's have these. The OP just wants
> to issue make release in his top-level dir instead of walking through
> all subdirs...
> 

Sorry for entering this discussion a little late but has anyone tried to do
qmake -recursive -after "CONFIG+=release"
then just run make normally? it should then build everything in release 
mode. Of course you would have to run qmake again so that you'll get the 
  original make behaviour back.

--
 [ signature omitted ] 

Message 8 in thread


Andreas Pakulat <apaku@xxxxxx> wrote on 08/29/2006 04:18:57 PM:

# > I don't think this is really a solution, though.
#
# That isn't even the same problem. The OP's problem is that the Makefile
# generated by qmake in the top-level dir doesn't have a release or debug
# target. However the non-subdirs Makefile's have these. The OP just wants
# to issue make release in his top-level dir instead of walking through
# all subdirs...

Well, it *kind* of is... but I don't think it's an acceptable one.

That is to say, it allows one to build both release and debug from
a SUBDIRS project - but it still doesn't let you *choose* between
one or the other.

--
 [ signature omitted ] 

Message 9 in thread

On Thursday 24 August 2006 20:22, Simon Perreault wrote:
> I have a top-level .pro using the SUBDIRS template. All my other .pro
> use debug_and_release. I want to be able to to "make release" from the
> top-level directory. Currently, I get
>
> make: Nothing to be done for "release".
>
> What can I do?

Wait for Qt-4.2 (or perhaps it is possible to use the qmake of 4.2 with 
older versions of Qt4 also).

Anyway, in the current 4.2 snapshot, also the Makefiles generated for the 
SUBDIRS template contain "debug" and "release" targets. Works fine here 
(on Linux, didn't check with Windows yet).

Regards,
Bernd

--
 [ signature omitted ] 

Message 10 in thread

Bernd Brandstetter <bbrand@xxxxxxxxxx> wrote on 08/30/2006 01:53:18 AM:

# On Thursday 24 August 2006 20:22, Simon Perreault wrote:
# > I have a top-level .pro using the SUBDIRS template. All my other .pro
# > use debug_and_release. I want to be able to to "make release" from the
# > top-level directory. Currently, I get
# >
# > make: Nothing to be done for "release".
# >
# > What can I do?
#
# Wait for Qt-4.2 (or perhaps it is possible to use the qmake of 4.2 with
# older versions of Qt4 also).

Indeed yes; just run "configure" on a 4.2tp1 tree, and then copy the
generated qmake binary into your existing tree (backing up the old
qmake binary first, just in case).

You'll need to run my "patchqmake" binary on it to fix the hard-coded
paths:
http://lists.trolltech.com/qt-interest/2005-11/thread00257-0.html

# Anyway, in the current 4.2 snapshot, also the Makefiles generated for the

# SUBDIRS template contain "debug" and "release" targets. Works fine here
# (on Linux, didn't check with Windows yet).

Huh... come to think of it, you're right.  I'd noticed that it seemed to
work "sometimes"; the "sometimes" must have been dependent on which OS I
was running under, since I had 4.2tp1 on one of them :)

--
 [ signature omitted ] 

Message 11 in thread

> From: Andreas Pakulat [mailto:apaku@xxxxxx]
> Sent: Thursday, August 24, 2006 1:35 PM
> 
> On 24.08.06 15:16:51, Simon Perreault wrote:
> > Andreas Pakulat wrote:
> > >I haven't tested this, but did you try adding CONFIG +=
> > >debug_and_release in the top-level project file?
> >
> > Yes I did, and it did not seem to make any difference.
> 
> I think you should write a wishlist report to TT.
> 
If you look at src/src.pro, you can see how the Trolls worked around
this (not pretty).  
-----------------------------------------------------------------------
DISCLAIMER:  Information contained in this message and/or attachment(s) may contain confidential information of Zetec, Inc. If you have received this transmission in error, please notify the sender by return email.

Ce courrier électronique est confidentiel et protégé. L'expéditeur ne renonce pas aux droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il contient par une personne autre que le (les) destinataire(s) désigné(s) est interdite. Si vous recevez ce courrier électronique par erreur, veuillez m'en aviser immédiatement, par retour de courrier électronique ou par un autre moyen.
-----------------------------------------------------------------------

--
 [ signature omitted ] 

Message 12 in thread

On 24.08.06 13:45:31, Tom Matelich wrote:
> 
> > From: Andreas Pakulat [mailto:apaku@xxxxxx]
> > Sent: Thursday, August 24, 2006 1:35 PM
> > 
> > On 24.08.06 15:16:51, Simon Perreault wrote:
> > > Andreas Pakulat wrote:
> > > >I haven't tested this, but did you try adding CONFIG +=
> > > >debug_and_release in the top-level project file?
> > >
> > > Yes I did, and it did not seem to make any difference.
> > 
> > I think you should write a wishlist report to TT.
> > 
> If you look at src/src.pro, you can see how the Trolls worked around
> this (not pretty).  

I'd even go as far and say this is a pretty ugly hack.

Andreas

-- 
 [ signature omitted ] 

Message 13 in thread

Andreas Pakulat wrote:
> > If you look at src/src.pro, you can see how the Trolls worked around
> > this (not pretty).  
> 
> I'd even go as far and say this is a pretty ugly hack.

For about 20 years, I considered TeX the worst example of a
'programming language' that is actively used.

Looks like qmake is nowadays a tough contender...

Andre'

--
 [ signature omitted ] 

Message 14 in thread

qmake is not a programming language

On 8/24/06, André Pönitz <andre@xxxxxxx> wrote:
> Andreas Pakulat wrote:
> > > If you look at src/src.pro, you can see how the Trolls worked around
> > > this (not pretty).
> >
> > I'd even go as far and say this is a pretty ugly hack.
>
> For about 20 years, I considered TeX the worst example of a
> 'programming language' that is actively used.
>
> Looks like qmake is nowadays a tough contender...
>
> Andre'
>
> --
> To unsubscribe - send a mail to qt-interest-request@xxxxxxxxxxxxx with "unsubscribe" in the subject or the body.
> List archive and information: http://lists.trolltech.com/qt-interest/
>
>


-- 
 [ signature omitted ] 

Message 15 in thread

On 25.08.06 09:28:27, Patrick Stinson wrote:
> qmake is not a programming language

Well, for Qt4's qmake we have:

variable's and assignment
loops
conditionals

No types, or better said, only strings and list of strings. And
functions to handle these. 

We also have ways of executing other programs.

Not too bad for a small imperative programming language.

;-)

Andreas

-- 
 [ signature omitted ] 

Pages: Prev | 1 | 2 | Next