Here's a small tool, which I made mainly for the people like vid, who'd like to have -D option in command line. It's a non-SSSO command line overlay for fasm, which provides few "unorthodox" options that fasm itself does not.

First of all, it allows to specify multiple source files in the command line, which will get assembled as one - this way you can, for instance, include some macro package before the main program you are assembling, like:

Code:

fa optimization_macros.inc my_program.asm -o my_program.exe

Note the -O switch used to specify output file. If it is not specified, the default will be used, which is "a" with a extension appropriate for the output format (like a.exe or a.obj). Such neutral name is used because of the fact, that there may not be single source file (it's similar to how ld linker generates the default output as a.out).

Other additional options are: -D for defining symbolic variables from command line, -I for defining include paths (same as defining them with INCLUDE variable), -L to make listing (FA has listing generator built-in).

And it's currently only for Windows, sorry.

Hi Tomasz,
Thank you very much, nice tool!
So, if I understood it correctly, we don't need to call fasm.exe from the command line to compile files but fa.exe , which calls fasm.exe?

best regards

Thanks Tomasz, I can hardly keep up with all the updates! One question, does the command line version for Windows use the fasmw.ini file? Would it be hard to add this to the command line version also?

Tomasz Grysztar wrote:

Here's a small tool, which I made mainly for the people like vid, who'd like to have -D option in command line. It's a non-SSSO command line overlay for fasm, which provides few "unorthodox" options that fasm itself does not. First of all, it allows to specify multiple source files in the command line -O switch used to specify output file. -D for defining symbolic variables from command line -I for defining include paths (same as defining them with INCLUDE variable), -L to make listing (FA has listing generator built-in).

COOL.

Quote:

And it's currently only for Windows, sorry.

Would be nice to have this for DOS also. I personally don't need "-D" and "-O" (since format binary as "DLL" rocks ), but "-L" is interesting

madmatt wrote:

> One question, does the command line version for Windows use the fasmw.ini file?

NO. RTFS

Tomasz Grysztar wrote:

And it's currently only for Windows, sorry.

Will it be included in future official FASM Win32 packages?

EDIT: In particular, this subforum doesn't allow non-registered viewers to download attachments, so that's part of my concern.

EDIT #2: I would honestly prefer it named to "fas" or "fasmw32" or similar.

Quote:

madmatt wrote: Quote: > One question, does the command line version for Windows use the fasmw.ini file? NO. RTFS

RTFS?

"Read The Freakin' Source", I assume.

rugxulo wrote:

prefer it named to "fas" or "fasmw32" or similar.

Why ? NO

Maybe FASMEVIL would be a good name for a hack not tolerable in the "official" version

Please recount all the problems it caused while it was active, aside from couple of design freaks (including Tomasz ) hating it.

rugxulo wrote:

"Read The Freakin' Source", I assume.

I think he means read the first post, you can define an INCLUDE variable. I'll do this and see if it does the same as the fasm.ini file.

Hello,

Notice that launching "FA" concurrently (like with GNU make) makes corruption as it uses always an intermediate file named "A.$$$". It might be better if the "A.$$$" file takes a random name each time.

Regards

Nice tool!
Is it possible to add an option to generate the MAP file?
Like the file with addresses for all non-local labels.

AsmGuru62 wrote:

Nice tool! Is it possible to add an option to generate the MAP file? Like the file with addresses for all non-local labels.

Do you mean something like what TOOLS/WIN32/SYMBOLS generates?

It is perfect!

I must filter it out a little, I need to exclude stuff from FASM INC files, but that is what I was looking for.

Why use this style of coding ? I think you can stores a byte, word, or doubleword from the AL, AX, or EAX register, respectively, into the destination operand. So what it's your idea ?

convert_definition:
mov esi,[ebx+4]
mov eax,'defi'
stosd
mov eax,'ne '
stosd
dec edi