Edit Rename Changes History Upload Download Back to Top

i-views' build scripts

Here at intelligent views (i-views) the build process consists of the following "components": Deployment is initiated manually by evaluating:

PrerequisitesBrowser deployBatchFile: 'makeNameOfProduct.bat' targetDirectory: 'TargetDirectory'

The deployment requires no user interaction from here on. The PrerequisitesBrowser

The product batch file then sets the parameters (environment variables) required to run the automated deployment image. A product batch files look like this:


set FILE=imagefilename
set PARCELS=RootParcelA, RootParcelB
set ORGEXE=visual.exe
set ICON=ka.ico
set SPLASH=ka.bmp
cd make
call make.bat
cd ..

The generic batch file then launches the deployment image. This deployment image is basically a plain base image + RuntimePackager + some automation code. The automation code loads the required parcels and the RTP file and then builds the target image. After this, the make.bat uses ResHacker to build a Windows executable with the correct splashscreen, icon, and VM. Deployment is now done.

Unit tests are not automatically performed, there is another batch file that can run Unit Tests in virtually any image (by loading some Unit Tests parcels and an headless Testrunner).


There are two annoying aspect of this build process:

To improve the build process, I'm currently considering the following changes:
Holger Kleinsorgen (h.kleinsorgen _at_ i-views.de)


Edit Rename Changes History Upload Download Back to Top