Command line parameters

Hi Friedrich,

I seem to recall mentioning this, but don't remember if I actually did
or just planned to!

As I add more and more compiler variables that I pass from Build
Automator to SB and plan to add more, I'm getting concerned that I'll
hit the command line limit.

Help and Manual has for many years had an option where you can write
variables and values out to an INI file and then pass the name of that
INI file to H&M command line compiler. The Variables.txt file looks
like this:

VERSION=2018.10.2459.320
VERSION_MAJOR=2018
VERSION_MINOR=10
VERSION_BUILD=2459.320
RELEASEDATE=October 8, 2018
AUTHOR=Arnór Baldvinsson
COPYRIGHT=Copyright ©2007-2018 Icetips Alta LLC.

What are the chances of implementing something like this in SB? It would
take out the possibility of running into command line limitations and it
helps a bit with debugging too as you can then refer to the file for
what exactly was being passed into SB to determine on which side problem
with passed data is.

Best regards,

--
Arnor Baldvinsson
Icetips Alta LLC

Hi Arnor,

> What are the chances of implementing something like this in SB? It would
> take out the possibility of running into command line limitations and it
> helps a bit with debugging too as you can then refer to the file for what
> exactly was being passed into SB to determine on which side problem with
> passed data is.

It's already possible to handle this with some hand-coding in the script
editor (processing a "response file" for non-interactive installations).

But I like your idea. I'll give it some thoughts on how to add this as a
built-in feature (with no coding required).

Friedrich

For the IDE itself, of course it can't be script coded. But I'll use a
similar method to feed the compiler.

Very good idea, Arnor. Thank you for your suggestion!

Friedrich

Hi Friedrich,

> Very good idea, Arnor. Thank you for your suggestion!

Thank the H&M guys<g> But as I try to standardize things more and more
between BA and SB it means more and more parameters with more and more
text and information. 8K, or whatever it is that fits on the command
line, is not a whole heck of a lot of data.

Best regards,

--
Arnor Baldvinsson
Icetips Alta LLC

Hi Arnor,

>> Very good idea, Arnor. Thank you for your suggestion!
>
> Thank the H&M guys<g> But as I try to standardize things more and more
> between BA and SB it means more and more parameters with more and more
> text and information. 8K, or whatever it is that fits on the command line,
> is not a whole heck of a lot of data.

The shocking news is that I have already implemented this on December 16,
2008. And it is part of SetupBuilder since June 27, 2009. In other words,
more than nine years ago. Ouch! But it's not in the documentation :-(
Argh!

Please try:

SB10.EXE /C "C:\test\sample.sbp" /CVL "c:\test\variables.txt"

variables.txt format:

PRODUCTNAME=Arnor
RELEASEDATE=October 8, 2018

Does this work?

Did I implement it before the H&M guys? <g>

--
Friedrich Linder
Lindersoft | SetupBuilder | www.lindersoft.com
Voice: +1.954.537.3701 | Fax: +1.954.537.3702

--SetupBuilder "point. click. ship"
--Helping You Build Better Installations
--Create Windows 10 ready installations in minutes
--Official COMODO Code Signing and SSL Certificate Partner

BTW, multiple compiler variable list files are allowed:

SB10.EXE /C "C:\test\sample.sbp" /CVL "c:\test\variables.txt" /CVL
"c:\test\yada.txt"

And on top of this you can use BOTH variable and variable file(s):

SB10.EXE /C "C:\test\sample.sbp" /CVL "c:\test\variables.txt" /CVL
"c:\test\yada.txt" /CV YADA "123"

Nice feature <g>. Good to know it's available.

Friedrich

Hi Friedrich,

> The shocking news is that I have already implemented this on December 16,
> 2008. And it is part of SetupBuilder since June 27, 2009. In other words,
> more than nine years ago. Ouch! But it's not in the documentation :-(
> Argh!

It was probably a request from yours truly<g> I *thought* you had, but
couldn't find anything in the help.

> Please try:
>
> SB10.EXE /C "C:\test\sample.sbp" /CVL "c:\test\variables.txt"

This is excellent! Thank you so much!

Best regards,

--
Arnor Baldvinsson
Icetips Alta LLC

>Nice feature <g>. Good to know it's available.

You have surprised yourself! LOL

Passing parameters to an SB-installer, however not such a plethora like Arnor
is juggling, is on my list for the next week (hopefully).

My Client-EXE will check for an update on the server, eventually d/l and call
this silent SB-installer with its own path as parameter via CHAIN(). The silent
installer the will use this path as the target to replace the existing
installation, then call the newly installed EXE and the user can continue.

Doable, I guess.

Regards,
Wolfgang Orth
www.odata.de

Please note:
From time to time it happens, that I overlook a reply to my postings.
Please don't be angry.
In case of an emergency, try to contact me via mail.

Bitte beachten:
Von Zeit zu Zeit passiert es mir, dass ich Antworten auf meine Postings übersehe.
Bitte nicht böse sein.
Im Notfall bitte Kontakt per Mail versuchen.

Wow, great timing for me to see this. I was thinking earlier today that I
needed this.

Greg Berthume

Hi Friedrich,

> And on top of this you can use BOTH variable and variable file(s):
>
> SB10.EXE /C "C:\test\sample.sbp" /CVL "c:\test\variables.txt" /CVL
> "c:\test\yada.txt" /CV YADA "123"
>
> Nice feature <g>. Good to know it's available.


I trust it will make it into the help so we can BOTH remember what's in
there?<bg> It's happened to me couple of times I got a great idea for a
new class. Started writing and it started looking more and more
familiar. Yep, had written it years ago and completely forgot about it<g>

Best regards,

--
Arnor Baldvinsson
Icetips Alta LLC