Post a reply to the thread: BUG: Compiling from command line?
Click here to log in
What's the name of our main installation product (in uppercase letters), directly followed by the current year?
You may choose an icon for your message from this list
Will turn www.example.com into [URL]http://www.example.com[/URL].
Re: BUG: Compiling from command line? Perfect! Thanks for the update. Friedrich
Re: BUG: Compiling from command line?
Re: BUG: Compiling from command line? Using the absolute path fixed the issue! Thanks!
Re: BUG: Compiling from command line? Hello, where is your "System450.sbp" located? I would suggest to specify the fully qualified pathname. For example: call "C:\Program Files (x86)\Lindersoft\SetupBuilder 10 Developer\SB10.EXE" /CS "c:\yada\System450.sbp" /LX Public Does this help? If there is still an issue, please send your System450.sbp project file to our support [at] lindersoft [dot] com and we'll check it (we'll be back from vacation on next Monday). Thanks, Friedrich
BUG: Compiling from command line? Running this on command line: Code: call "C:\Program Files (x86)\Lindersoft\SetupBuilder 10 Developer\SB10.EXE" /CS ProjA.sbp /LX Public Produces this result: Attachment 4581 However, when I open SetupBuilder 10 UI and compile, it works fine. If I type in file paths using absolute paths, then compiling from command line works; so the issue is that compiling from command line is ignoring Compiler Variables. My output directory is set to Code: [SB_PROJECT]\Release The only thing that I could think that would do it is, I'm testing SetupBuilder 10 using the Trial Version, so when I run the command line, I get the prompt that I'm using a trial version.
BUG: Compiling from command line?
call "C:\Program Files (x86)\Lindersoft\SetupBuilder 10 Developer\SB10.EXE" /CS ProjA.sbp /LX Public
[SB_PROJECT]\Release
Forum Rules