ilink32 (32-bit) build link errors after updating to 2024.7

Albert Wiersch

I updated to SyntaxEdit 2024.7 and am now getting link errors for 32-bit builds:

[ilink32 Error] Error: Unresolved external 'ScriptIsComplex' referenced from D:\ALC_COMPONENTS_12\LMDVCL2024\LIB\D29\WIN32\LMDRTSYNTAX.LIB|LMDSedView

[ilink32 Error] Error: Unresolved external 'ScriptStringAnalyse' referenced from D:\ALC_COMPONENTS_12\LMDVCL2024\LIB\D29\WIN32\LMDRTSYNTAX.LIB|LMDSedView

[ilink32 Error] Error: Unresolved external 'ScriptString_pSize' referenced from D:\ALC_COMPONENTS_12\LMDVCL2024\LIB\D29\WIN32\LMDRTSYNTAX.LIB|LMDSedView

[ilink32 Error] Error: Unresolved external 'ScriptStringCPtoX' referenced from D:\ALC_COMPONENTS_12\LMDVCL2024\LIB\D29\WIN32\LMDRTSYNTAX.LIB|LMDSedView

[ilink32 Error] Error: Unresolved external 'ScriptStringXtoCP' referenced from D:\ALC_COMPONENTS_12\LMDVCL2024\LIB\D29\WIN32\LMDRTSYNTAX.LIB|LMDSedView

[ilink32 Error] Error: Unresolved external 'ScriptStringFree' referenced from D:\ALC_COMPONENTS_12\LMDVCL2024\LIB\D29\WIN32\LMDRTSYNTAX.LIB|LMDSedView

[ilink32 Error] Error: Unable to perform link

Fortunately Windows 64-bit (Modern) still works.

UPDATE 1: Well a clean new 32-bit VCL app with an editor component seems to run and link... so I guess I'll try to figure out what's going on... but maybe you have an idea? Maybe related to the 'SyntaxEdit: Win64x linking problem fix.' in 2024.7?

UPDATE 2: Found the problem. I had removed '#pragma comment(lib, "Usp10") ' but it seems this is still needed for 32-bit builds (but apparently not 64-bit builds).

Rafael Maricca (LMD)

Thank you for the feedback!

Eugene Balabuev (LMD)

Yes, at my side new clean VCL project with SyntaxEdit controls compile and link well in all supported compilers, including 32bit. Something is missing in your old cproj file. I suggest to compare it with clean project as a text. Try to search for Usp10 for example.

Albert Wiersch

Thanks. Good idea.