digit
07-14-2009, 04:43 PM
I'm working on a VBP project now that simply calls another VBP project with some special parameters to override project-level macros.
This works very well for our purposes, but sometimes we pass additional command-line parameters to control various options like where to put source files pulled from the repository. The problem comes when I try to pass one of these additional parameters to the "parent" project: naturally, they are not also passed to the chained one.
I can workaround this by manually specifying parameters that might be used (like BUILDS_ROOT=%BUILDS_ROOT%), but obviously this isn't very flexible. Is there an easy way to propagate command-line parameters to chained projects? Or is there just an easier way to do what I am doing?
Thanks in advance.
This works very well for our purposes, but sometimes we pass additional command-line parameters to control various options like where to put source files pulled from the repository. The problem comes when I try to pass one of these additional parameters to the "parent" project: naturally, they are not also passed to the chained one.
I can workaround this by manually specifying parameters that might be used (like BUILDS_ROOT=%BUILDS_ROOT%), but obviously this isn't very flexible. Is there an easy way to propagate command-line parameters to chained projects? Or is there just an easier way to do what I am doing?
Thanks in advance.