Multiple destination target
Hi all,
I need that on the end of compiling the target should be copied on multiple destination paths. May I specify it in .pro file?
I use
target.path = $DESTDIR
INSTALLS += targer
for specify destination dir.
I've tried to specify multiple destination paths in target.path variable but it doesn't work.
Any idea?
Thanks,
Michele De Candia
Re: Multiple destination target
I don't know if this is possible, and I would be surprised if it was.
What do you need that for?
Re: Multiple destination target
Why don't you make a script for each platform on which you plan running your app?
Re: Multiple destination target
Hi need to distribute the target executable on more machines by nfs shared partitions and the idea is to make it by "make install"
Re: Multiple destination target
What about if I need to execute some batch command at the end of install process and I want to do that into "make install" command?
Re: Multiple destination target
I use something like this to perform a regular install:
INSTALL_SPECS += wwwidgets.prf
mkspecs.files = $$INSTALL_SPECS
mkspecs.path = $$[QT_INSTALL_DATA]/mkspecs/features
INSTALLS += mkspecs
I think that you can use the ".command" property to issue the command to be executed. I'm not sure of that though, but it's worth to try. If not, then simply provide multiple install entries, possibly using some kind of stencil.
Re: Multiple destination target
Quote:
Originally Posted by
wysota
I use something like this to perform a regular install:
INSTALL_SPECS += wwwidgets.prf
mkspecs.files = $$INSTALL_SPECS
mkspecs.path = $$[QT_INSTALL_DATA]/mkspecs/features
INSTALLS += mkspecs
I think that you can use the ".command" property to issue the command to be executed. I'm not sure of that though, but it's worth to try. If not, then simply provide multiple install entries, possibly using some kind of stencil.
I can't find documentation about ".command" property . Where I can fid it?
Re: Multiple destination target
It might not be documented. First try if it works at all, because it might not. It holds the command to execute. Usually it's used to define external compilers, but there is a chance install targets are implemented as such as well.
Re: Multiple destination target
On which variable I may try .command property?
Re: Multiple destination target