The following line results in a linker error:

include \masm32\include\

but this one not:


I think there should be a problem with environment variables.
So when ever i want to use and debug.lib the following error hits me in the brain:

fatal error A1000: cannot open file : \masm32\include\

(is there an environment var that I've not set?)

if you dont help me I'll get back to VC++!! :(
Posted on 2003-03-11 03:23:18 by titanwalker

Can you check the location of your include files?

I think your file is located in the bin directory.You should put it
to your include directory.(masm32\include)


Posted on 2003-03-11 03:50:02 by Vortex
Specifying \masm32\include\ is telling masm to look in current directory\masm32\include\
since the current directory is usually the directory containing the source file, unless you're in the habit of copying the masm32 directory to every asm project, then it's not difficult to see why you're getting file not found errors

if masm32 is on the c drive then:
c:\masm32\include\ would do the trick.
Posted on 2003-03-11 10:20:20 by MArtial_Code
I am surprised!!
The story:
I have installed masm32 in my F: drive
But my projects are in G: drive.
I accidentally moved a .asm file to f:\masm32\ and it assembled nicely!!!
of course with the Include directives i mentioned earlier.

So whenever I assemble any .asm file from any folder in my F:
drive every thing is OK.

But From other drives i get that linker error again.

And about the debug.lib:
If you view it with a hex Editor you will see lines like this:
Defaultlib: /masm32/lib/kernel32.lib ....

So how can i redirect linker!!!There is noway(I think:)).(don't think about linker switches ,I tried them all.)
Any idea why all these happen!
Posted on 2003-03-14 13:48:17 by titanwalker

it can be an environment issue, just check your %INCLUDE% variable and paths containing.

Without telling a path explicitly, compiler makes lookup in current dir first, following all the paths from the var. It's possible you left another version if WINDOWS.INC on the path. Try to check for multiple instances of this file on your drives.

Posted on 2003-03-15 03:40:36 by _Servil_