News:

MASM32 SDK Description, downloads and other helpful links
MASM32.com New Forum Link
masmforum WebSite

Masm + GoLink

Started by Vortex, July 08, 2005, 08:17:03 AM

Previous topic - Next topic

jorgon

The same can now be done with GoAsm + GoLink.

Instead of using includelib as you would if you were using MASM+GoLink, if you are using GoAsm+GoLink the syntax is:-


#dynamiclinkfile user32.dll, kernel32.dll, comctl32.dll


the comma is optional and separate lines are ok, too.

The above declaration is in the asm source.  It works the same way as MASM's includelib (the information is passed to the linker by the assembler using the .drectve section in the object file).  So this avoids having to refer to the dll in the linker's command line or command file.  #dynamiclinkfile only works if you use GoAsm+GoLink.  Use includelib if you are using MASM+GoLink.  The reason why in both cases you specify the dll itself rather than a lib file, is that GoLink does not refer to lib files when finding out which dlls provide the functions required.  Instead at link-time it looks inside the dll itself.  Since most of these dlls are already in memory anyway this is also efficient.


Author of the "Go" tools (GoAsm, GoLink, GoRC, GoBug)

Vortex

Hi Jeremy,

Thanks for the info :U