_d_
July 14th, 2005, 01:27
hi,
i have written a disassembler which puts out the data in nasm format + all exports and imports.
but if i assemble the the .asm source with -fobj i can link it with alink but alink doesn't genereate a .lib file, now i cannot link the dll into my vc projects.
if i compile the .asm source with -fwin32 nasm tells me that the command
import apiname modulename
is not correct
the only solution i know to link my nasm generated obj with vc link is that i write
write all imports this way
import _apiname@arguments modulename
but if i disassemble a dll i don't know the @arguments, without parsing the coresponding .lib
thanks for help
i have written a disassembler which puts out the data in nasm format + all exports and imports.
but if i assemble the the .asm source with -fobj i can link it with alink but alink doesn't genereate a .lib file, now i cannot link the dll into my vc projects.
if i compile the .asm source with -fwin32 nasm tells me that the command
import apiname modulename
is not correct
the only solution i know to link my nasm generated obj with vc link is that i write
write all imports this way
import _apiname@arguments modulename
but if i disassemble a dll i don't know the @arguments, without parsing the coresponding .lib
thanks for help