i coded this tool to direct output dll functions into fasm inc format,
please hand remove some functions name if they are conflict with asm reserved words.
one must use complete file path when specify the dll file.
if you put this tool in PATH, to run it, you must still type dll2inc
.exe
example output
+----------------------------------------------------+
| dll2inc - export dll functions into fasm inc file. |
+----------------------------------------------------+
[ usage ] = D:\dll2inc.exe D:\dlldir\dllfilename.1-2.3.dll
[ output ] = D:\dlldir\dllfilename.1-2.3.inc
------------------------------------------------------
successful exported inc file is inside specified dll directory
D:\fasmw17117>dll2inc.exe d:\PROJECT\sqlite3.dll
[pdllh] . . . . . . . . . . . . . . . . = 0x60900000
e_magic = 0x5A4D
e_lfanew . . . . . . . . . . . . . . . . = 0x80
e_lfanew addr = 0x60900080
signature . . . . . . . . . . . . . . . = 0x4550
magic = 0x10B
RvaAndSizes . . . . . . . . . . . . . . = 16
IMAGE_DATA_DIRECTORY[0].VirtualAddress = 0x60972000
NumberOfNames . . . . . . . . . . . . . = 206
AddressOfNames = 0x7236C
206 functions exported
08/02/2014
a. uploaded new set of gtk dll inc files (should be ok now) into google drive.
b. uploaded binary dll2inc.exe with fixes
07/02/2014
a. fix cinvoke fopen,oufwrite,<'wb+',0>, no b open using fopen will cause another 0x0D appended while fprintf.
b. dll name that contained - (dash) will get changed into _ (underscore), otherwise fasm will detect that dll name as something invalid.
c. source file updated.