Kinook Software Forums

Go Back   Kinook Software Forums > Visual Build Professional > [VBP] General Discussion

Thread Tools Rate Thread Display Modes
Old 03-26-2008, 02:10 PM
tan125 tan125 is online now
Registered User
Join Date: 08-30-2007
Location: PA
Posts: 15
Send a message via Yahoo to tan125
Project vs. Temporary macros

What is the difference between a project macro and a temporary macro? Temp macros are specific to the instance of VBP, but I guess what I'm asking is what defines the scope of a project for a project macro? If I have a project macro, and I have a step where I call a different .bld file, do I need to pass it into that .bld file or is this considered within the scope of the project?
Reply With Quote
Old 03-26-2008, 02:20 PM
kinook kinook is online now
Join Date: 03-06-2001
Location: Colorado
Posts: 5,797
Project macros are specific to a given project (.bld file). They are not automatically passed to project B when called from project A. You can pass them as temporary macros to a chained project using the Parameters tab of the VisBuildPro Project action.

Temporary macros are specific to a given VBP instance and are not persisted to disk. They are created by passing macro values on the command-line, a Set Macro action, and by various actions when a step of that action type is built (i.e., COPY_COPY_COUNT, PROCFILES_FILENAME, etc.), prompting for undefined macros, etc., and usually deleted at the end of a build. They have a higher precedence than project macros (a temporary macro X will be used over project macro X).
Reply With Quote

Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

All times are GMT -5. The time now is 07:21 AM.

Copyright 1999-2021 Kinook Software, Inc.