Unattended Build - 6.0

[nancyp]

With Setup 6.0 I am having difficulty getting anything to work with unattended build.

I made a .bat file and entered the information in the manual page 260.

With only the full path to SUF60Design.exe, it still will not work.

I figured maybe it would not work from the .bat logic. If that is so what COMMAND line does run it or am I just doing something wrong?

I made an .ini file for the /B option. Can anyone post an example that works?

[Lorne]

Re: Unattended Build - 6.0

[Note: I'm moving this thread to the SF General forum...doesn't really belong in the Suggest New Feature forum ]

What did you put in the batch file?

It's possible that an error in the batch file might be preventing the line from executing. Have you tried testing the command line you're using by typing it directly at a command line prompt (i.e. not in a batch file)?

It could also be a problem with the paths you're using in the command -- either not properly quoted or missing entirely. But that's only a guess based on limited information.

It's a bit hard to post an example that "works" without knowing what project file and unattendended build INI file you want to open and where they're located on your system. We'll have to make do with a hypothetical situation:

SF6 path:
"C:\Program Files\Setup Factory 6.0\SUF60Design.exe"

Project file path:
"C:\Output\foo.sf6"

Unattended build INI file path:
"C:\Output\foo build.ini"

Command line I used:
"c:\Program Files\Setup Factory 6.0\SUF60Design.exe" "C:\Output\foo.sf6" /B:"C:\Output\foo build.ini"

Contents of "foo build.ini" file:
[Constants]
#foo#=Here's looking at you, kid

I just built a setup that replaced "#foo#" on the Welcome screen with "Here's looking at you, kid."

[nancyp]

Re: Unattended Build - 6.0

The difference that made it work was the following:

In the manual the syntax is shown as:

SUF60Design.exe D:\foo.sf6 "/B :\release build.ini"

The quote was in front of the /B:

In your response to me it was:
SUF60Design.exe D:\foo.sf6 /B:"D:\release build.ini"

The quote was moved. That made it work. You might want to check the documentation page 260.

[nancyp]

Re: Unattended Build - 6.0

BTW - The BUILD variables in the .ini file do those replace, overwrite and/or append
to the BUILD variables in the project?

Are there any certain variables that must be added?

What order are they loaded?

Can I use them to replace or correct the values in the Build Variables that are in the project? (version numbers and release dates things like that)

[Lorne]

Re: Unattended Build - 6.0

Originally posted by nancyp:
The difference that made it work was the following:

In the manual the syntax is shown as:

SUF60Design.exe D:\foo.sf6 "/B :\release build.ini"

The quote was in front of the /B:

In your response to me it was:
SUF60Design.exe D:\foo.sf6 /B:"D:\release build.ini"

The quote was moved. That made it work. You might want to check the documentation page 260.

It should work either way...I just tried it with the quote before the /B: instead of after it, and it worked fine here. (You're the second person to point that out, but this is the second time I tested it both ways, and found both ways to work...)

BTW, there should not be a space between the /B and the : (not sure if that was just a typo above in your reply?).

[nancyp]

Re: Unattended Build - 6.0

Lorne,

I searched my computer and I removed the bat file, since it did not work at all.

I know I was typing it at a prompt but since the path names I am using are very long, it may have been a typo. I moved a few things around to simplify the paths.

But while you are looking at this section look at the example on page 261:

It says: C :\xyz.sf6

what is that?
Thanks for your help. I will be able to recreate my builds quickly from one prompt.

[Lorne]

Re: Unattended Build - 6.0

Ouch...that is an actual, real, veritable typo.

It should be:

D:\xyz.sf6

and not

C:\xyz.sf6

(Grumble. Sometimes rapid application development has its disadvantages...)

[nancyp]

Re: Unattended Build - 6.0

I understand. It was part of what was so confusing. Two examples, both different.

Can any default paths be assumed to shorten the path names in the commands?

[Lorne]

Re: Unattended Build - 6.0

Originally posted by nancyp:
BTW - The BUILD variables in the .ini file do those replace, overwrite and/or append
to the BUILD variables in the project?

I believe they get appended to the list of design-time constants...I'm not 100% sure on that, though. In practice, assigning a value to #foo# in the .ini file will override any previous assignment to #foo# made in the design environment.

Are there any certain variables that must be added?

Not sure what you meant there?

What order are they loaded?

Design-time constants are replaced by their values at build time, before the setup executable is built. The assignments are made in the same order as the design-time constants are listed on the Design-time Constants tab of the Project Settings dialog.

Can I use them to replace or correct the values in the Build Variables that are in the project? (version numbers and release dates things like that)

If by "build variables" you mean design-time constants, then yep, I'm pretty sure that you can replace those with items in the ini file.

[Lorne]

Re: Unattended Build - 6.0

nancyp, what is the exact command line you were using in the batch file (when it didn't work with the quote in front of it)?

I'd like to do some more testing and get to the bottom of the whole page 260 thing.

(Feel free to post or email the batch file if you want.)