|
#1
|
|||
|
|||
Command-Line Response File
Does either VisBuildPro.exe or VisBuildCmd.exe support the concept of a "response file"? I have potentially a large number of macros and such that I would like to supply as startup parameters and an old-fashioned response file seems like the best idea. I would want to use syntax something like “VisBuildCmd.exe @myopts.txt”
Any suggestions if this is not supported? |
#2
|
|||
|
|||
Not currently. Some options:
1) Create a one-step VBP project with a VisBuildPro Project action, configure the step with all desired options and macros, then launch that project from the command-line (i.e., VisBuildCmd /b Master.bld). 2) Create a VisBuildPro Project step as above, click the Create Scheduled Task button on the Project tab (copy/paste the command-line from the task's Run field if needed elsewhere), then delete the step. 3) Load many temporary macro values from a file at the start of the project rather than passing on the command-line (see attached sample). 4) Write a script front-end to VBP that takes a response file of flags and invokes VBP from its values (see attached sample). We'll also consider adding such a capability in a future release. |
#3
|
|||
|
|||
I like option 3 that you suggested. The example was very helpful.
Thanks! |
|
|