SDK not compiling due to _readscreen dependencies

SDK not compiling due to _readscreen dependencies

For anyone hitting a dependence issue when compiling with the new SDK (from 0.91), which might look like this: 1>adpcore.lib(rand_win.obj) : error LNK2019: unresolved external symbol __imp__DeleteDC@4 referenced in function _readscreen 1>adpcore.lib(rand_win.obj) : error LNK2019: unresolved external symbol __imp__DeleteObject@4 referenced in function _readscreen 1>adpcore.lib(rand_win.obj) : error LNK2019: unresolved external symbol __imp__GetBitmapBits@12 referenced in function _readscreen 1>adpcore.lib(rand_win.obj) : error LNK2019: unresolved external symbol __imp__BitBlt@36 referenced in function _readscreen 1>adpcore.lib(rand_win.obj) : error LNK2019: unresolved external symbol __imp__GetObjectA@12 referenced in function _readscreen 1>adpcore.lib(rand_win.obj) : error LNK2019: unresolved external symbol __imp__SelectObject@8 referenced in function _readscreen 1>adpcore.lib(rand_win.obj) : error LNK2019: unresolved external symbol __imp__CreateCompatibleBitmap@12 referenced in function _readscreen 1>adpcore.lib(rand_win.obj) : error LNK2019: unresolved external symbol __imp__GetDeviceCaps@8 referenced in function _readscreen 1>adpcore.lib(rand_win.obj) : error LNK2019: unresolved external symbol __imp__CreateCompatibleDC@4 referenced in function _readscreen 1>adpcore.lib(rand_win.obj) : error LNK2019: unresolved external symbol __imp__CreateDCA@16 referenced in function _readscreen 1>..\..\..\Dark Basic Pro\Compiler\plugins-user\appupplugin.dll : fatal error LNK1120: 10 unresolved externals I solved it by simply adding Gdi32.lib into my list of required LIB files and it compiled fine. I often search the forum when I hit a problem on compiling a new SDK, so hopefully you found this and your problem went away :)
The Game Creators (www.thegamecreators.com)
3 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.

Thanks Lee/Rick :) Nice tip.

Hey, Thanks a Million. Just was updating to final release of SDK, and this solved it. Thanks!

Paul

Leave a Comment

Please sign in to add a comment. Not a member? Join today