Index
> Windows > include variable PATH problem on x64. |
| Author |
|
|
revolution 21 Dec 2012, 08:33
fasm doesn't read the PATH variable. Use INCLUDE instead.
It is documented BTW. |
|||
21 Dec 2012, 08:33 |
|
|
Overflowz 21 Dec 2012, 14:20
I know that it doesn't read but I had exact same thing on x86 and worked perfectly.
--- p.s I've added INCLUDE variable in environment settings, but got still same problem.. Code: include 'win32a.inc' ;FILE NOT FOUND. include '%INCLUDE%\win32a.inc' ;FILE NOT FOUND. |
|||
|
21 Dec 2012, 14:20 |
|
|
revolution 21 Dec 2012, 14:38
What is the setting of your INCLUDE variable? Does is point to your installation folder?
Code: include=c:\fasm\include |
|||
|
21 Dec 2012, 14:38 |
|
|
Overflowz 21 Dec 2012, 14:41
I'm so dumb.. I modified system's environment variable instead of INI files include
 please, delete this useless topic. |
|||
|
21 Dec 2012, 14:41 |
|
|
nmake 21 Dec 2012, 18:31
Today's windows is the continual work of perfection for 27 years, all of the years passed was nothing but corrections and improvements, what a large group at microsoft can't do in 27 years combined, you can't expect a single man to have everything fall in place at first attempt. So you're not stupid, I present to you these good news.
 |
|||
|
21 Dec 2012, 18:31 |
|
|
zzj0402 23 Dec 2012, 05:56
According to Grysztar, Tomasz. in Flat Assembler 1.70 Programmer's Manual on page 7-8, it seems to have a way of making the include to work by setting the environment variable named INCLUDE to the path of the include directory.
Setting assembler IDE is not the only way to resolve the problem of not compiling the include directive. However setting environment variable only is not working. The setup seems only assembler IDE specific. So, is it necessary to set environment variable? Or it could be used in some cases? |
|||
|
23 Dec 2012, 05:56 |
|
< Last Thread | Next Thread > |
Forum Rules:
|