On 4/12/10 11:13 AM, Daniel Teske wrote: > On Monday 12 April 2010 16:01:36 ext Stephen Chu wrote: >> Hi >> >> Is there a list of available variables that we can use in the custom >> build steps? I see the $BUILDDIR in the working directory. Is there >> anything else like the built app filename, etc. that can be used in the >> command field? > > No, that's currently all there is. What's your use case? >
I'd like to copy the built binary back to the project folder. I have several PCs that I work from during different time of the day. Each of them can have different shadow build setup. Using absolute path will not work across them. So the least I will need are the path to the built binary and the path to the project folder. I can construct the built binary path by using hard-coded name in the command arg field. But I will have to remember going back to change it if I ever rename the project output. Hard-coding the project will not work since the project file may reside in different locations between setup. And you can never have too many predefined macros/variables anyway. :) Maybe using environment variables for these? Setting them up before calling the custom step? -- Stephen Chu <mailto:[email protected]> <http://www.ju-ju.com> _______________________________________________ Qt-creator mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-creator
