Gen 8.6 build error: "cannot open input file 'delayimp.lib' "

[Nikolaos Karpodinis]

Hello,
  i've installed GEN 8.6 in a Windows 10 pc, and trying to make either a windows (Oracle) generation or a Windows (Oracle) cooperative server generation, receive the same error:
LINK : fatal error LNK1181: cannot open input file 'delayimp.lib'

Before this error, i was receiving "cannot open include file 'afxres.h' ", but this was fixed after followed the instructions of another thread.

It's installed both Visual Studio 2017 & 2019 in the PC, tried to put either of the paths in the enviroment variables, but with no success, built still failing(i restart build tool after every change)

Any suggestions?

Thank you,
Nick
================================================================


CA Gen Build Tool Compose
Copyright (c) 2016 CA. All rights reserved.


Compose Succeeded

Microsoft Windows [Version 10.0.19042.867]
(c) 2020 Microsoft Corporation. All rights reserved.

C:\Program Files (x86)\CA\Gen86\Gen>"C:\Program Files (x86)\CA\SharedComponents\JRE\OpenJDK\jdk8u212-b04-jre\\bin\java.exe " -classpath "C:\Program Files (x86)\CA\Gen86\gen\bt\bt.jar" com.ca.gen.bt.Execute "C:\Models\referece\BOS_BTC.ief\c\B90001S.bat"
Initial search for build executables
NMAKE.EXE, proc.exe, HHC.EXE, CL.EXE, LINK.EXE, RC.EXE

--- Found NMAKE.EXE

--- Found proc.exe

--- Found HHC.EXE

--- Found CL.EXE

--- Found LINK.EXE

--- Found RC.EXE


...Copying C:\Program Files (x86)\CA\Gen86\gen\.\STUBORAN.OBJ to C:\Models\referece\BOS_BTC.ief\c\OBJC\STUB.OBJ

=====================Load Module Script Environment=================
Operating System: WINDOWS
"Database Manager: ORACLE"
Environment: WINDOWS
Language: C
Codepage: 1253
Model: BOS.BTC.100.004
Subset: ALL
Level: 9.2.A6.01

==============================SUMMARY===============================
Summary of Load Module Script Results for Load Module B90001S:
==============================LEGEND================================
Legend: ... precedes information about an operation to be performed.
--- precedes results from an operation which just completed.
*** precedes error info from an operation which just failed.
(Symbols preceding info are indented to convey step levels.)

==============================DETAILS===============================
Details of B90001S Load Module Script Results:

Microsoft (R) Program Maintenance Utility Version 14.00.24210.0
Copyright (C) Microsoft Corporation. All rights reserved.

...Compiling Stub resources
copy "C:\Program Files (x86)\CA\Gen86\gen\version\applno.bat" "C:\Models\referece\BOS_BTC.ief\c\applno.bat"
1 file(s) copied.
call "C:\Models\referece\BOS_BTC.ief\c\applno.bat" YES "C:\Models\referece\BOS_BTC.ief\c\" B90001S "C:\Program Files (x86)\CA\Gen86\gen\" GUI
APPLNO.BAT : CA Gen BUILDTIME and BUILDVER update file
rc -r -DWIN -D_AFXDLL -DIEF_BITMAP=. -I"%IEF_BITMAP%" -I"C:\Models\referece\BOS_BTC.ief\c\." -I"C:\Program Files (x86)\CA\Gen86\gen\version" -DCUSTOMER_APPL -fo"C:\Models\referece\BOS_BTC.ief\c\STUB.RES" "C:\Models\referece\BOS_BTC.ief\c\stub.rc"
Microsoft (R) Windows (R) Resource Compiler Version 6.3.9600.17336

Copyright (C) Microsoft Corporation. All rights reserved.


...Linking Load Module stub B90001S
link /NOLOGO /SUBSYSTEM:WINDOWS -entry:WinMainCRTStartup -out:"C:\Models\referece\BOS_BTC.ief\c\B90001S.EXE" /DELAYLOAD:WRGN.DLL "C:\Models\referece\BOS_BTC.ief\c\OBJC\STUB.OBJ" "C:\Models\referece\BOS_BTC.ief\c\OBJC\STUBMAIN.OBJ" "C:\Models\referece\BOS_BTC.ief\c\STUB.RES" @"C:\Models\referece\BOS_BTC.ief\c\STUB.LNK"
LINK : fatal error LNK1181: cannot open input file 'delayimp.lib'
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.16.27023\bin\Hostx86\x86\link.EXE"' : return code '0x49d'
Stop.
****************************
Link step for STUB.EXE using C:\Models\referece\BOS_BTC.ief\c\STUB.LNK failed with errors.
****************************
File Not Found
IEFSIGNAL:FAIL
*** Build for Load Module B90001S Failed. ***
Important! Review above for any errors.

[Andy Hebert]

Nick,
  I reviewed your OUT file and see that some PTFs may not be applied.  Below are the requirements that you need at a minimum.  Not knowing what you changed for the 'afxres.h' error, they may need to be backed out.  I recommend opening a case with Gen Support to work through the problem(s).  I am available to open the case and work with you if you like, just let me know.

Required Gen 8.6 PTFs for VS2017 or VS2019 support are:
VS2017:
Gen 8.6 Complete: WKS86200/SO09618
The VS 2017 support was originally delivered with a series of *861* PTFs but WKS86200 supersedes them (CA Gen 8.6 > Technical Requirements > Change Summary)
WKS86200 is also the baseline for all new 8.6 PTFs, so as a matter of course, it should be installed to be able to install any later PTFs.

VS 2019:
Gen 8.6 Complete: WKS86200/SO09618
TSN86209/ SS13873
BTN86201/SS13871
RTN86208/SS13872

Regards,

Andy Hébert
Broadcom Inc.
Principal Support Engineer

[Nikolaos Karpodinis]

Hello Andy,
  thanks for the response, the WKS86200 and the GEN86202 PTFs are installed. As for the afxres.h & some other initial build errors, i followed the instructions and selected some more options at the Visual Studio setup (https://knowledge.broadcom.com/external/article?articleId=124419 & https://knowledge.broadcom.com/external/article?articleId=132576). 
Yes, if you can, plz. open a case to check what causes the problem.

Thanks,
Nick

[Nikolaos Karpodinis]

After all, i found what caused build error about delayimp.lib during linking.
The problem was that Build Tool configuration has, by default, settings for Visual Studio 2015, instead of VS2017 that we have in our PCs.

More specific, you must change the setting in Build Tool Profile (BUILD Tool -->Tools --> Profile Manager (select the generation profile) --> OPTIONS --> OPT.VSVERSION and change the default value VS140(that is for Visual Studio 2015) to VS150(for VS 2017).

P.S. as Gen 8.6 installation document recommends, if you change the above value, you must also change the value of OPT.BUILD_SRC from "NO" to "YES"  at "C" section of the Build Profile.

After these changes, build was successful.