OSDev.org

nexos wrote:

PeterX wrote:

bzt wrote:Now where did you get that? FASM can generate lot more kind of object files than NASM. Look up "format" directive in the documentation.

http://flatassembler.net/docs.php?artic ... _manual#14 says:

Currently the only available choice is "format binary"

I hope this is outdated and false.

Greetings
Peter

I think that manual you pointed to is for fasmg.

Thanks forcorrecting me. You are right, it is about "Fasm g"
The correct manual is this:
http://flatassembler.net/docs.php?article=manual#2.4
which says what bzt said (PE, COFF, ELF).

PeterX wrote:Thanks forcorrecting me. You are right, it is about "Fasm g"
The correct manual is this:
http://flatassembler.net/docs.php?article=manual#2.4
which says what bzt said (PE, COFF, ELF).

Yes, and just for the records, fasmg can output in many formats too (probably even more than fasm). From the doc

The only built-in instruction that resides in that namespace is the "binary", but additional ones may be defined in form of macroinstructions.

That's because fasmg's philosophy is that it has only the very essence of an Assembler, and provides everything else (instruction sets as well as output formats) through macros. Here's a tutorial on how to add new output formats to fasmg, exampled with PE+ and ELF. (Just for the records, fasmg is shipped with several include files for many output formats, and you can download many more. Here's the include file generating MachO and Android Dalvik bytecode for example)

Cheers,
bzt

Hi Ankit,
viewtopic.php?f=13&t=37193
Was a good discussion with some off topic posts.
Fasm is a respected and well documented assembler. However, I would say do whatever that fits your boat.
--Thomas