i found out i changed stance on the "-D" (define symbol) and "-i" (additional include path) problem, after trying to code in conventional way - create multiple object files.

For usual way of using FASM, where you produce executable directly, you really need just to change your thinking, and docs say. But with conventional programming, where you divide your code among many .obj files, this is a must-have. Without this, FASM really can't be effectively used for such programming IMO.

Note that the second way, even though less confortable, is little bit more powerful, because it allows mixing languages (use C libraries, create asm libraries for C projects, etc...).

Here is the real-world problem: In FASMLIB i have functions "text.write.b2hex", "text.write.w2hex", "text.write.d2hex", etc...
Then, i have functions "stdout.write.XXX", which are just wrappers to "text.write.XXX", they add one extra argument to stack.

FASMLIB can be used both by including it's source (typical FASM way), or by linking to .lib file.

For source, declaring such wrappers is enough:
This way i don't have to type same code for each function.

But when i want to create .lib file, i need every such call wrapper in separate file. With -D switch, it would be enough to have single file, which would use caller-defined symbol, and assemble it multiple times.

Do you know of any other solution than -D switch for this?

PS: I believe this is same problem that arafael had some time ago, i just can't find it now

simply put: SSSO principe is not so nice when you need to output more than one destination file

"but you can just use environment variables".

I have to agree, though -D is immensively useful. Producing debug/release builds, and a number of other things. The SSSO principle means you have to edit files or kludge around to achieve the same things as -D could do for you...

Then you should need more than one source file, as the output is unequivocally determined by a single one.
You may not like it, but it has its rules. "Dura lex, sed lex", as they say.

Hi vid,
I would do it like this:

include CONFIG.INC in you sources
then in your build script do the equivalence of:

kandamun: that's what's called a HACK