Post-Build actions using qmake

[bhs-ittech]

Is it possible to define some actions in the project file
which is executed after the build is done?

[fullmetalcoder]

This is documented...
These two variables may reveal interesting if you're looking for some automation : PRE_TARGETDEPS and POST_TARGETDEPS.

[bhs-ittech]

But aren't they just for libraries, and other build targets?

What I had in mind was something like zipping, moveing, and/or deleting files.

[aMan]

how could that be platform independant?

[fullmetalcoder]

how could that be platform independant?

By using a couple of scopes :

mytarget.target = ...
mytarget.depends = ...
 
unix {
    mytarget.commands = ...
}
 
win32 {
    mytarget.commands = ...
}
 
macx {
    mytarget.commands = ...
}

mytarget.target = ...
mytarget.depends = ...

unix {
    mytarget.commands = ...
}

win32 {
    mytarget.commands = ...
}

macx {
    mytarget.commands = ...
}

To copy to clipboard, switch view to plain text mode 

Note : the last time I tried using this mechanism, everything worked fine except for a single thing : I did not see any difference between PRE_TARGETDEPS and POST_TARGETDEPS... Whatever I did, my additional target got processed BEFORE compilation... Is is me or is it a bug in qmake?

[bhs-ittech]

Thanks,
that cleared it up for me.
Now I'm able to do what I intended, and find the relevant information
in the documentation

Again thanks alot

[wysota]

Whatever I did, my additional target got processed BEFORE compilation... Is is me or is it a bug in qmake?

I think it is meant to be that way. At least that's what the docs suggest.

As far as I understand it, it is like this:

$(LINKER) $(PRE_TARGETDEPS) -o $(TARGET) $(POST_TARGETDEPS)

So both PRE and POST have to be built before the actual target. Those variables only determine the moment when they will be linked (the order of linked libraries is sometimes important).