Command-line build checks licence
Posted: Fri Mar 07, 2008 11:47 am
Hi,
I have recently seen several issues where building an install kit using the command line while I have the IDE open causes:
- the IDE to complain about too many licences being used and shutting down
- the install kit generated on the command line showing the trialware "go to the InstallAware" web site at the start of the installation.
I thought the command line wasn't supposed to need an extra licence.
If I do not have the IDE open, the command line seems to work fine.
I have InstallAware Studio Admin V7 (lonepine_rtm071107) with a floating licence.
The command line call to InstallAware in the script is
"%INSTALLAWARE%\\miabuild.exe" "%INSTALL_DIR%\\kit.mpr" /r /b=1 "/o=%KITROOT%" %VARIABLES%
Most of the time, it is a support engineer creating the actual kit, though I am the only person doing script development. I cannot ask the support engineers to check with me before running the script - that would generate too much overhead (for all of us), and I though it was the point of not needing a licence for scripting.
This is not only annoying if I'm working in the IDE, it wastes my time when I have to support our support engineers (who are creating the kits) and it is potentially embarrassing if it gets out to a customer.
Please fix this (or give us a separate "build-only" licence which won't cause this behaviour).
Thank you,
Ian Brockbank
I have recently seen several issues where building an install kit using the command line while I have the IDE open causes:
- the IDE to complain about too many licences being used and shutting down
- the install kit generated on the command line showing the trialware "go to the InstallAware" web site at the start of the installation.
I thought the command line wasn't supposed to need an extra licence.
If I do not have the IDE open, the command line seems to work fine.
I have InstallAware Studio Admin V7 (lonepine_rtm071107) with a floating licence.
The command line call to InstallAware in the script is
"%INSTALLAWARE%\\miabuild.exe" "%INSTALL_DIR%\\kit.mpr" /r /b=1 "/o=%KITROOT%" %VARIABLES%
Most of the time, it is a support engineer creating the actual kit, though I am the only person doing script development. I cannot ask the support engineers to check with me before running the script - that would generate too much overhead (for all of us), and I though it was the point of not needing a licence for scripting.
This is not only annoying if I'm working in the IDE, it wastes my time when I have to support our support engineers (who are creating the kits) and it is potentially embarrassing if it gets out to a customer.
Please fix this (or give us a separate "build-only" licence which won't cause this behaviour).
Thank you,
Ian Brockbank