Linking problems: where to find the libraries?

CyberShadow

Hello,

I'm having some problems with linking my application. The problem is that although the WindowsAPI project has the headers for everything, there's still the problem with the libraries. DM's and DMD's libs are obviously sub par, and I'm not sure of the right way to make my own. Using implib creates unusable libraries - OPTLINK keeps looking for names such as "_SQLGetInstalledDrivers@12", and DLLs don't have the argument information (stuff after @), and I don't know how to make OPTLINK ignore it. So far the only solution I can think of is writing my own .DEF files by hand.

jcc7 · Joined: 22 Feb 2004 Posts: 657 Location: Muskogee, OK, USA

CyberShadow · Posted: Wed Jan 09, 2008 11:06 am Post subject:

Thanks, I appreciate that Smile

Two more questions:
1) I noticed that on the Wiki page you mentioned how to create import libraries from DLLs. I'm wondering if this is of any use when linking to D code? As I understood it, DMD creates linkage symbols in the form _function@argsize, and there's no way to get the argsize thing from the DLL. Theoretically the linker could discard the part after @, but OPTLINK doesn't seem to be able to do that?

2) I noticed that when importing win32.windows, there are always some linker warnings about missing libs: mpr.lib, advapi.lib, imm32.lib, lz32.lib, rpcns4.lib. I guess those are specific to mingw?

yidabu · Joined: 21 Apr 2007 Posts: 87

some Windows libs under DWin.lib
_________________
D yuyan