Fatal Compiler Error [3]

[NewsArchive]

Hi Friedrich,

I just had this happen in by Build Automator install script:

Linking kernel...
Fatal Compiler Error [3]: Cannot link
sbkernel: [C:\PROGRA~1\LINDER~1\SETUPB~3\Bin32\SBKERNEL.LIB],
[C:\Products\BuildAutomator\Latest\Build
Automator\BuildAutomatorInstall_6.2.1354".lsp]

But it ONLY happens if I run it from Build Automator, i.e. via the
command line compiler.

I ran a full build earlier today and it was fine and I've built several
builds of BA in the past week or so. Never seen this before. Works
fine on other installs with the command line compiler... Works on the
web update installer as well.

Any idea what is going on? It compiles fine from the SB IDE.

Best regards,

--
Arnor Baldvinsson
Icetips Alta LLC

[NewsArchive]

Hi Friedrich,

> I just had this happen in by Build Automator install script:

Just FYI, the parameters I use for the main install is:

C:\Program Files\Lindersoft\SetupBuilder 10 Developer\SB10.EXE /C
"C:\Products\BUILDA~1\Latest\BUILDA~1.SBP" /CV EXENAME
"BuildAutomatorInstall_6.2.1354"".exe" /CV IT_COPYRIGHT "©2016 Icetips
Alta LLC" /CV PRODUCTVER "6.2.1354" /CV OUTPUTDIR
"C:\Products\BuildAutomator\Latest\Build Automator"

and the command line I use for the web install is:

C:\Program Files\Lindersoft\SetupBuilder 10 Developer\SB10.EXE /C
"C:\Products\BUILDA~1\Latest\BUILDA~2.SBP" /CV EXENAME
"BuildAutomatorInstall_6.2.1354.exe" /CV IT_BUILDNUMBER "1354" /CV
PRODUCTVER "6.2.1354" /CV OUTPUTDIR
"C:\Products\BuildAutomator\Latest\Build AutomatorWeb"

First it does code signing etc. and then the SB Log continues with:

Code signed successfully: C:\Products\BuildAutomator\Latest\Program
Files\Icetips\Build Automator\Automator.dll
Scanning folder: C:\Products\BuildAutomator\Latest\Program Files\Common
Files\Icetips\Build Automator\Plugins\*.*
Scanning folder: C:\Products\BuildAutomator\Latest\Program
Files\Icetips\Build Automator\*.*
Excluding: C:\Products\BuildAutomator\Latest\Program Files\Icetips\Build
Automator\BuildAutomator.exe
Scanning folder: C:\Products\BuildAutomator\Latest\All Users\Application
Data\Icetips\Build Automator\Actions\*.vatn
Scanning folder: C:\Products\BuildAutomator\Latest\All Users\Application
Data\Icetips\Build Automator\Templates\*.*
Scanning folder: C:\Products\BuildAutomator\Latest\All Users\Application
Data\Icetips\Build Automator\Actions\*.actn
Enable .REG Host Service Encryption: No
Script(s) processed
Generating Code...
OK
Building executable...
Approx. Stub size: 24,235 bytes
Linking kernel...
Fatal Compiler Error [3]: Cannot link sbkernel:
[C:\PROGRA~1\LINDER~1\SETUPB~3\Bin32\SBKERNEL.LIB],
[C:\Products\BuildAutomator\Latest\Build
Automator\BuildAutomatorInstall_6.2.1354".lsp]

Just for fun I did a "Save As" on the SB project file to
BuildAutomatorEXE.sbp and it also fails with the same error:(

I'm dead in the water with this. Let me know if you want the script or
if you have any ideas to try out.

This script hasn't changed since december. I took a copy of it from
when I last built it and it also fails. Tried one from August 2015 and
it also fails:(

I'm on the latest Setup Builder version according to the "Help | Check
for updates"

Best regards,

--
Arnor Baldvinsson
Icetips Alta LLC

[NewsArchive]

Hi Arnor,

The " after your 1354 seems to be incorrect:

[C:\Products\BuildAutomator\Latest\Build
Automator\BuildAutomatorInstall_6.2.1354".lsp]

Friedrich

[NewsArchive]

Hi Friedrich,

> "BuildAutomatorInstall_6.2.1354"".exe" /CV IT_COPYRIGHT "©2016 Icetips

Thanks for seeing the extra " - spotted it - see the double " after
1354? Fixed:)

Best regards,

--
Arnor Baldvinsson
Icetips Alta LLC

[NewsArchive]

Hi Friedrich,

>> "BuildAutomatorInstall_6.2.1354"".exe" /CV IT_COPYRIGHT "©2016 Icetips
>
> Thanks for seeing the extra " - spotted it - see the double " after
> 1354? Fixed:)

What had happened was that I added a variable to my BA script so that I
can add "_BETA" to the exe name if it's a beta build so it's easy for me
to see what's what. I had - wrongly - initialized the variable to ""
where it should have been simply empty (I use " in BA for single quotes
so it's easier to deal with quoted strings in there;) I had looked and
looked at the command line but never spotted the ""

So, thanks again for your eagle eyes:)

Best regards,

--
Arnor Baldvinsson
Icetips Alta LLC