Better explanation of polink errors

Got an idea for enhancing PureBasic? New command(s) you'd like to see?
MachineCode
Addict
Addict
Posts: 1482
Joined: Tue Feb 22, 2011 1:16 pm

Better explanation of polink errors

Post by MachineCode »

I just installed 4.60 RC1 but one of my apps has died, with the following error. I assumed it was a UserLib problem (because they usually are), and I re-installed all UserLibs with their 4.60 version (except ComatePlus, which doesn't have a 4.60 yet), but the error remains.

Is there a way this sort of error message can be handled differently? To show a better explanation of what's broken? Thanks.

Code: Select all

---------------------------
PureBasic - Linker error
---------------------------
POLINK: error: Unresolved external symbol '_PB_FindString'.
POLINK: fatal error: 1 unresolved external(s).
---------------------------
OK
---------------------------
Microsoft Visual Basic only lasted 7 short years: 1991 to 1998.
PureBasic: Born in 1998 and still going strong to this very day!