SetupBuilder command line interface
Could someone confirm that the SetupBuilder V6.5 Developer edition command
line interface works as documented? e.g. SBuilder /C "MyProject.sb6" should
compile the project "MyProject".
This "unattended build" capability is vital for a project I'm doing for a
client and I can't get the evaluation version of SB V6.5 Dev edition to do
anything with the command line (other than throw the message that it is the
"Evaluation Version"). In other words, it doesn't build the setup program
the way I _THINK_ it should. This may be a limitation in the eval version
but per the docs the eval version is "fully functional" so I wouldn't think
so.
I emailed the question to Lindersoft on Friday but of course haven't heard
back yet - it IS the weekend after all!!
Incidentallly I own SB V4 and use it for my installs. I haven't purchased
the later versions of SB simply because (until now) SB 4 did everything I
needed.
Thanks,
Al
Re: SetupBuilder command line interface
> This "unattended build" capability is vital for a project I'm doing
Cant pass the Joel test without it.
--
Mark Riffey
http://www.rescuemarketing.com/blog/
Re: SetupBuilder command line interface
Re: SetupBuilder command line interface
Al,
> "Joel test"??
http://en.wikipedia.org/wiki/The_Joel_Test
--
Lee White
http://CWaddons.com
http://LodestarSoftware.com
http://DeveloperPLUS.com
Programmer: code writer working with a schema provided by a DBA
DBA.......: egghead who designs database schemas
Developer.: drain bamaged masochist that does BOTH!
Re: SetupBuilder command line interface
Thanks for the explanation.
Al
Re: SetupBuilder command line interface
Hi Al,
>Could someone confirm that the SetupBuilder V6.5 Developer edition command
>line interface works as documented? e.g. SBuilder /C "MyProject.sb6" should
>compile the project "MyProject".
Verified, it works. You need to make sure that the path to the
SBuilder.exe is correct and also that the path to your project is
correct, i.e.:
"C:\Program Files\LinderSoft\SetupBuilder 6 Devloper\sbuilder.exe" /C
"C:\products\ITUtilities\Latest\ITUtilities.sb 6"
You get a Wait cursor and then it's done and the exe is updated<g>
The log file goes where it should and will report errors if any. If
no errors are detected during the build, the log file is removed.
The help topic of "Command Line Options (Compiler)" describes the
options that you have. I've only tested for the log file creation
that the /C actually works - it does:)
Best regards,
Arnór Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com
Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php
Re: SetupBuilder command line interface
Arnor,
Is the log file you mention the "compiler.txt" the docs refer to for compile
errors?
Al
Re: SetupBuilder command line interface
Hi Al,
>Is the log file you mention the "compiler.txt" the docs refer to for compile
>errors?
Yes, I think that's what it was called. It is only created IF there
is an error during the compile process. If no error occured the file
does not exist. So it's very easy to check for the file existence -
if it's there, there was an error, if not, the script compiled without
an error. The file includes basically the same thing as you see on
the compiler window, i.e. what it did, where it failed etc.
Best regards,
Arnór Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com
Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php
Re: SetupBuilder command line interface
Hi Al,
I checked our records and an email went out to you on Saturday morning. I
did not bounce back (I think).
Friedrich
Re: SetupBuilder command line interface
Friedrich,
You're probably right. I haven't been to work to check my emails (it IS the
weekend after all!).
Al