Break of Patch Requirements

kehagiem · Post by **kehagiem** » Sun Apr 19, 2009 4:10 am

The use of compiler variables to customize setup at build time and have setups for different products is really a nice feature to have, when only very few things change between them, having a unique setup project.

However, how such approach doesn't break the Patch requirements when the elements that I need to have different are: Product Name, Product Code, Product Version and files/features and such differentiation breaks the Patch Requirements?

MichaelNesmith · Post by **MichaelNesmith** » Sun Apr 19, 2009 9:05 am

As long as the compiler variable values are the same in the patch reference setups and the patch being built, you should not run into any issues.

kehagiem · Post by **kehagiem** » Mon Apr 20, 2009 1:46 am

So in this case, is it possible to configure in the Compiler Variables section the following:

1. Path to custom build output folder
2. Product Code

MichaelNesmith · Post by **MichaelNesmith** » Mon Apr 20, 2009 10:01 am

Yes, of course!

kehagiem · Post by **kehagiem** » Mon Apr 20, 2009 11:17 am

can you please so me how, i.e. the variable names?

MichaelNesmith · Post by **MichaelNesmith** » Mon Apr 20, 2009 5:34 pm

Use whatever names you like, and enter in those variables using the form #NAME# into the respective hard coded fields. Then just use whatever values you like for those newly created compiler variables (use the Project Options dialog to define them, and you can assign/override default values there, or use the command line build tool).

kehagiem · Post by **kehagiem** » Tue Apr 21, 2009 1:33 am

Very well, thanks.