+ Reply to Thread
Page 1 of 4 123 ... LastLast
Results 1 to 10 of 40

Thread: Command Line Options

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1

    Default Command Line Options

    Hey,

    i have two problems:

    i want to save my compiler variable when i make a setup with the function #Edit INI

    next try - i load this ini file with command line option /CV

    my problem: #Edit INI work only when i put a "=" at the INI item field - example:

    Don´t work: _AUSWAHLRN_ "[_AUSWAHLRN_]"
    work: _AUSWAHLRN_="[_AUSWAHLRN_]"

    the biggest problem is - that the command line field is to short - with only 127 characters.

    or can i read direkt a ini file by command line ?

  2. #2
    Join Date
    Mar 2004
    Posts
    4,307

    Default Re: Command Line Options

    Hello,

    Well, the general Windows INI format is:

    [section]
    keyname=value

    In other words, your _AUSWAHLRN_ "[_AUSWAHLRN_]" is not an INI item at all ;-) So it is the expected Windows behavior that this does not work! keyname=valuename translates into your _AUSWAHLRN_="[_AUSWAHLRN_]" which does work fine.

    Friedrich

  3. #3

    Default Re: Command Line Options

    Quote Originally Posted by linder View Post

    [section]
    keyname=value

    In other words, your _AUSWAHLRN_ "[_AUSWAHLRN_]" is not an INI item at all ;-) So it is the expected Windows behavior that this does not work! keyname=valuename translates into your _AUSWAHLRN_="[_AUSWAHLRN_]" which does work fine.

    Friedrich
    hey,

    That's right, and I can live with it

    But what should I do when i have more then 127 charaters ?!

  4. #4
    Join Date
    Mar 2004
    Posts
    4,307

    Default Re: Command Line Options

    Quote Originally Posted by Galedon View Post
    But what should I do when i have more then 127 charaters ?!
    Not sure what 127 byte limitation means in this case. Yes, there is a Windows/DOS command line limitation (depends on different factors), but if you are using a batch file, this is definitely >127 bytes. And there is no 127 bytes command line limitation in the SetupBuilder command line compiler per-se.

    See attached screenshot. I passed a 200 byte value to the [TEST1] compiler variable without any problem.

    Friedrich
    Attached Images Attached Images   

  5. #5
    Join Date
    Mar 2004
    Posts
    4,307

    Default Re: Command Line Options

    BTW, if you are interested, I can post my test .sb7 project and the batch.bat file.

    Friedrich

  6. #6

    Default Re: Command Line Options

    ok

    with a batch file its work - but your function Run Command Line - or Run Program => Command Line have the limit.

    I have make a batch file - with 739 characters.

    But it is true that I only have one compiler variable can be passed by command line?

    In the online help I was able to find anything.

  7. #7
    Join Date
    Mar 2004
    Posts
    4,307

    Default Re: Command Line Options

    Hello,

    You can pass multiple compiler variable values via the sb7.exe command line compiler.

    No, not our Run Program command line function has a 127 bytes limit. There is a specific Windows limit (but it depends on the Windows version).

    Friedrich

  8. #8

    Default Re: Command Line Options

    Quote Originally Posted by linder View Post
    Hello,

    You can pass multiple compiler variable values via the sb7.exe command line compiler.

    No, not our Run Program command line function has a 127 bytes limit. There is a specific Windows limit (but it depends on the Windows version).

    Friedrich
    i have 15 compiler variable - the setup take only the first !

    i use windows 7 - and your function Run command Line can only this length of string:

    12345678901234567890123456789012345678901234567890 12345678901234567890123456789012345678901234567890 12345678901234567890123456789012345678901234567890 12345678901234567890123456789012345678901234567890 12345678901234567890123456789012345678901234567890 1234

  9. #9
    Join Date
    Mar 2004
    Posts
    4,307

    Default Re: Command Line Options

    The entry fields have a limit of 254. This has nothing to do with the command line length of your compiled .exe.

    Create a runtime variable, e.g. %MY_COMMANDLINE% and then you can use a command line value of up to 1,024 bytes.

    BTW, if you can only pass one value then you are doing something wrong. See attached screenshot.

    The following command line passes two compiler variable values to the compiler:

    sb7.exe" /C "c:\sbtest\galedon.sb7" /CV TEST1 "AAAAAAAAAA" /CV TEST2 "BBBBBBBBBB"

    BTW, make sure you have defined the compiler variables in the Compiler Variables Visualizer!

    Hope this helps.

    Friedrich
    Attached Images Attached Images  

  10. #10

    Default Re: Command Line Options

    lol

    i have found the first problem - i have make sb7.exe" /C "c:\sbtest\galedon.sb7" /CV TEST1 "AAAAAAAAAA" TEST2 "BBBBBBBBBB"

    and not sb7.exe" /C "c:\sbtest\galedon.sb7" /CV TEST1 "AAAAAAAAAA" /CV TEST2 "BBBBBBBBBB"



    ok - but i have now the next problem:

    command line: /CV _AUSWAHLRN_ "|Standard - Deutsch/English|Fränkische|REHAU"

    setup select only Standard & Rehau

    Command Line: /CV _AUSWAHLAW_ "|standard - update"

    setup select two lines !

    Command Line:
    /CV _TREIBER_ "|BDE|DAO|ALADDIN_DIAGNOSTICS|HARDLOCK|HASP|HELPRE G|OPENDWG_CAE|ZIPDLL"

    Setup forget one line!
    Attached Images Attached Images    

+ Reply to Thread

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Tags for this Thread

Posting Permissions

  • You may post new threads
  • You may post replies
  • You may not post attachments
  • You may not edit your posts
  •