ml64 A1000 error through Visual Studio 2017: a problem of path?

PIERRE REISS LABORDE 101 Reputation points
2021-07-06T07:08:54.19+00:00

Let Dir a project directory, with a subdirectory Pierro (the project name). Inside Pierro, I edit 2 files Main.cpp and A.asm:

extern "C" int A ();
int main ()
  {
  return A ();
  }

and

.RADIX    16
.CODE
  PUBLIC  A
  A       PROC
  xor     eax,eax
  ret
  A       ENDP

Yesterday I downloaded and reinstalled properly Microsoft Visual Studio 2017 (version 15.9.36).
The subsystem is console. The config is debug. The platform is x64.
I replaced x86 by x64 in the Active solution platform.
masm (.targets, .props) is activated.
If I add the existing element Dir\Pierro\A.asm to the project, the build don't invoke ml64.
Else if I replace this file by its copy into the parent directory, the build invokes ml64, but cannot open A.asm (error A1000). And the command ml64.exe /c /nologo /Zi /Fo"x64\Debug\A.obj" /W3 /errorReport:prompt /TaA.asm stopped with the code 1.
Please, how to work around this path problem?

A build through a .bat file, outside Visual Studio, is OK. But debugging is then painful...

Not Monitored
Not Monitored
Tag not monitored by Microsoft.
35,815 questions
0 comments No comments
{count} votes

0 additional answers

Sort by: Most helpful