There's a suggestion to make INCLUDELIB (and maybe INCLUDEOBJ) directive. It's better than compiling to object formats (like format MS COFF) with linking by external linker because it's a problem to use standart includes (win32a.inc, win32ax.inc, etc) for MS COFF output format...
Joined: 16 Jun 2003
Location: Kraków, Poland
I consider the formatter module of fasm 1 already overblown and convoluted, that's why I generally stopped adding new features to it. As one may notice, for this reason I have implemented Mach-O format only for fasmg and the same may be true for other new formatters in the future. The fasmg macro implementations are much more flexible and easier to understand and customize by other people, too.
Joined: 24 Aug 2004
Location: Misner space
Jin X wrote:
So how can I use includes like 'win32a.inc' for MS COFF formats?
You will need to make other include files. As they exist now the win32* files are only meant to be used with the executable output format. You can still use the individual macro files for invoke and proc.
AFAIK, there’s plenty of formats for object files generated by different compilers (world doesn’t end outside of C/C++ ecosystem). Wouldn’t supporting only some of them make FASM too tied to particular toolsets, anyway?
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum