Licensing question - Using WinBatch Compiler in Automated Build System

[dmmWork]

Pretty much like the subject line says ... 

We have a handful of utilities written in WinBatch, compiled, and digitally signed which our Field Service staff use.

The source files & cmp files are stored in a version control system, but the actual compiling & digital signing of the
executables is done manually, on a single machine with a licensed copy of WinBatch+Compiler installed.

Is there a way to include only the files required to compile the source in to executables on our build system images
[these are VMware images, spun up & used only as needed], rather than installing and licensing a copy of WinBatch+Compiler
for each image ?

Our intent is not to avoid paying appropriate license fees, rather it is to simplify our software build process by automating
the WinBatch utility builds along with our other product & utility builds.

Thanks in advance for your time and attention,

-dmm

[Deana]

Sorry no, the Compiler does not support a way to include only the files required to compile the source in to executable on your build system images. However, if the process is only going to be used by one developer then have you considered creating a network share that points to your compiler? You could then include a batch compile script that uses the compiler from a server share to batch compile then sign your exes.

Reference:
http://techsupt.winbatch.com/webcgi/webbatch.exe?techsupt/nftechsupt.web+WinBatch/Compiler/Sample~Code~from~Users+Batch~Compile~UDF.txt
http://techsupt.winbatch.com/webcgi/webbatch.exe?techsupt/nftechsupt.web+WinBatch/64-bit+Code~Signing~an~EXE.txt

See also:
'Batch Compile' topic in WinBatch.chm
'IntControl 93' in WindowsInterfaceLanguage.chm

[dmmWork]

(snip!) ... However, if the process is only going to be used by one developer then have you considered creating a network share that points to your compiler? ... (/snip!)

Only one developer, but build machines are virtual, spin-on-demand ... and there are multiple events that can trigger a build ... so it sounds like we need to put a full copy of WinBatch+Compiler [fully licensed, of course] on the build machine image and use the batch build scripts from there.

Thanks for the quick response!

-dmm