Exportable project macros are not exported when overrided by temporary ones|

[ASolovey]

Hi, we're using VBP7 (7.0) and have just encountered a problem with subj.

Our vbp project contains a macro named 'BUILD_NO' which is marked as exportable. It is passed to the environment of programs being used during the build procedure.
So, when launched this from UI it works just fine.

The problem is that we need to override the value of this macro during automated build procedure when vbp is launched from the command line. We don that like this:

VisBuildCmd.exe BUILD_NO=123 build.bld

In this case the value of the temporary macro overrides the project macro. And all other parts of the project do 'see' that change.

BUT it is NOT exported! despite the project macro is marked as a exportable. That's the huge problem. The build process fails due to the fact that programs (specifically c++ compiler) do not have this macro in the environment.

Please let me know:
a) if this is the case
b) if this is a bug or by design behaviour
c) what's best workaround or solution

Best regards,
Alex.

[kinook]

A temporary macro created on the command-line will not update environment variables. Either:

1) Add a Set Macro step (with 'Add to environment variables' checked, Temporary macro type) to set BUILD_NO equal to %BUILD_NO%

This will force the BUILD_NO environment variable to be updated with the current BUILD_NO macro value.

or

2) Pass the value on the command-line with a different name (i..e, TEMP_BUILD_NO=123), and in the called project, add a Set Macro step (with 'Add to environment variables' checked, Temporary macro type, and a build rule to Build only if %TEMP_BUILD_NO% is undefined) setting BUILD_NO to %TEMP_BUILD_NO%


http://www.kinook.com/VisBuildPro/Ma...acroaction.htm
http://www.kinook.com/VisBuildPro/Manual/buildrules.htm

[ASolovey]

Thanks much,

did conditional macro replacement.