A self-compiled Windows Batch file for creating include files for static function import to FASM.

Why don't you just include it to your projects?

This macro is needed to create plug-in fasm files for static function import from Windows libraries. If the project does not have compiled libraries that are statically connected to the main file, there is no need for it. But if necessary, you can also update the plug-in files of static import of standard Windows libraries and add the missing ones. For myself, I rewrote the standard macros included in the fasm kit for static function import. I need the functions to be listed in a different order, but I was too lazy to rewrite them manually. In order to understand how it works, just try writing in the command line "export.cmd %WinDir%\system32\kernel32.dll", or "export.cmd %WinDir%\system32\winmm.dll".

Why don't you use import section to add missing/required functions from any library you want?

You can include your "plug-in" to
section '.idata' import data readable writeable
or use my multisection macro precent somewhere in this thread

There is a slightly different principle here. The import section is also used, but you have someone's library and some functions in it. The macro lists them from an already compiled library and forms it as a plug-in file added to the import section.