How would I go about breaking up source code into multiple files with FASM? From what I can understand all it is is a compiler and that's it. I need to be able to split up source code into modules/multiple files so that it's easier to manage.

Right now I'm using WinASM Studio.

Unfortunately there is no way to split up a project into multiple files in "C" style (i.e. "cc file1.c file2.c file3.c file4.c file41_2.c"), but you can use the "include" directive to include other files. Or, you could use object output and link them together, like most C projects do.

it is possible also to use COFF format and later linking. then you may use many asm-files - in WinAsm Studio in project explorer they have to be switched into "Module" mode: then when you will press "go all" they all will be assembled with fasm one bye one - i'll try to do example, but later - in few days.

Hmm, for C I have multiple C files but do "#include file.C", same with asm, but like the others said you will need a third party linker, GoLink or ALink aren't bad.

you can precompile procedure to pure code and use


but with FASM's speed i don't see reason why not just break one source into modules.

here is example of three asm-files of COFF format with later linking. needs scan.exe by Vortex and polink to link (based on example by Vortex).
linker is complaigning on some ".data" sections with different attributes - i had not understand it yet because i did it first time by myself
anyway it works "go all" log placed into "from_out.txt"

enjoy!

POLINK does this if the sections are merged, a '.flat' section could cause this but it is nothing to worry about.

i found the reason the linker complagning to:
in main.asm:

in message.asm:

first had attribute "uninitialized" due tu "?", second - "initialized"
i had renamed first section to ".udata":

and there will be no warnings more. as well as we can not sort initialized and not initialized data in section, combined from different objects, it is better to place them in separate sections. (".flat" section good for small applications.)
also, i agree: this way does not give us any advantage then usual "incs" if all asms will be assembled each time. this way can give advantage if make utility used, which checks if there is need to reassemble object or not.

regards!