On Thu, Sep 24, 2009 at 9:19 AM, Oswald Buddenhagen <
[email protected]> wrote:
> On Wed, Sep 23, 2009 at 09:15:16AM -0700, KC Jones wrote:
> > PRE_TARGETDEPS. That appears to be the missing ingredient.
> >
> note that it works only for makefile outputs. vcproj won't work.
>
> > BUT W.T.F.???!!!#####
> >
> two words: qmake sucks.
> patches are welcome, but be warned that if you supply one you out
> yourself as a masochist.
> and, btw, qmake is semi-officially slated for end-of-life, but nothing
> concrete is planned yet.
>
That's a shame. I really like qmake and I've found .pro files very readable
and minimlist next to say, CMake.
>
> > really don't want to add extra brittleness to my build scripts by
> > declaring particular OS paths.
> >
> qmake is surprisingly flexible - you could even write configure scripts
> with it. so there is no need to hard-code anything. if you formulate
> what *exactly* you want (say, in sh, perl or some pseudocode) i can give
> you a qmake "translation".
>
> > But now I have to take my LIBS decl and manually translate that into a
> > PRE_TARGETDEPS??? And remember to change this whenever libraries are
> > added or removed? Really?
> >
> no, you could make a function for adding a static lib which would add it
> to both the link lib and the pre-deps:
>
> defineReplace(asl) {
> PRE_TARGETDEPS += $$munge($$1)
> export(PRE_TARGETDEPS)
> return($$1)
> }
>
> LIBS += $$asl(foobar)
>
Can you provide a working example of this in use?
>
> or something similar ...
>
> and, fwiw, creator's own build system is a bonanza of, uhm, "advanced
> qmake examples".
> _______________________________________________
> Qt-creator mailing list
> [email protected]
> http://lists.trolltech.com/mailman/listinfo/qt-creator
>
_______________________________________________
Qt-creator mailing list
[email protected]
http://lists.trolltech.com/mailman/listinfo/qt-creator
