I have found the use of the "include" environment variable that specificies the FASM include location (which is actually %include% in DOS/Win32) to be distasteful.

Why? All of my other compiler tools use INCLUDE and they accept a list of directories in the form of "dirpath1;dirpath2;...;dirpathN". I have all these paths set at Win startup (or console startup) and, even more important, at Linux startup.

FASM wants a single directory and only its directory. So, in order to run FASM, I have to run a little batch script that overrides INCLUDE to set the single FASM directory. Why am I forced to fly in the face of convention?

As the way INCLUDE is commonly used is being violated, I suggest changing the variable to FASMINC. I have done so already in my source tree (you could even hot-patch the binary as the name is still 7 characters) and no longer need a startup script everytime I run FASM. I would like to propose that FASM be altered to fit better with the other tools out there.

Tomasz, what do you think about adding support of environment-variables which contains several pathes separated by the ; character - if you take my meaning?

Tommy

You can still use fasmw and it's fasmw.ini config file - this way you don't have to use neither INCLUDE nor FASMINC environment variables. For mode details see fasmw documentation.