Hi billy,
It isn't clear exactly what the problem is. "%include" is essentially a "cut and paste" operation, and it's pasted in where the "%include" occurs. For example, in the code Anonymous offers...
section .data
section .bss
section .text
; %include "include.asm"
; suppose our hypothetical include file,
; pasted in here, said:
section .data
foo db "this is my string", 10, 0
; and that's all
; whoops! we're no longer in "section .text"!
global _start:
_start:
; ...
There's a "__SECT__" macro known to Nasm that can be used to work around this. RTFM. In my opinion, this isn't worth bothering about. Just put your "section" directives where you need 'em - outside the "%include" - and you won't need to worry about "section" changes inside the "%include".
If that isn't your actual problem, show us some example code that illustrates it.
Best,
Frank