|
#1
|
|||
|
|||
Large project question
I've been asked to automate the build of several products that all comprise of several projects. I want to try and keep the amount of code that I would have to maintian to a minimum, and the amount of code that I can share across project as high as posible.
What would be the propper design for my scripts at that point ? The way I'm considering trying to do this is by creating one script that just searches a tree for build scripts and executes them. So it would work something as the following : build : product 1 -> script goes to the installer tree -> the install scripts will point at their dependancies -> dependancies will get executed ( projects get build ) -> the installers get build -> the product will get combined into a shipable format this is my first try at visual build so I'd like to get some feedback before I end up getting stuck somewhere along the line. Bas |
#2
|
|||
|
|||
Using subroutines and/or global subroutines can help to modularize your builds and reduce redundant code. And you can also generically build all existing build projects as you suggest using a Process Files step and child VisBuildPro Project step (demonstrated in the Chain.bld sample).
|
Thread Tools | |
Display Modes | Rate This Thread |
|
|