Visual C++ 6 Project with ASM module -> VS2003

I have a project myself and a friend worked on in Visual C++ 6 some time ago.

I am now trying to port this project to Visual C++ v7.1 as part of my move to Visual Studio.Net 2003.

One of the module in the file is a .ASM file which was assembled using MASM 6.11 as a custom build.

On attempting to assemble this project I am getting the following message:



Performing Custom Build Step

Microsoft (R) Macro Assembler Version 7.10.3077

Copyright (C) Microsoft Corporation. All rights reserved.

Assembling: and

MASM : fatal error A1000: cannot open file : and

Project : error PRJ0019: A tool returned an error code from "Performing Custom Build Step"


This command line for this custom build is:

ml /Cp /I. /c /coff /Zi /Fo"$(OutDir)"\"$(InputName)".obj "$(InputPath)"



Answer this question

Visual C++ 6 Project with ASM module -> VS2003

  • Gonzalo123

    ------- Build started: Project: WinSTon, Configuration: Release|Win32 -------

    Command Lines
       
    Creating temporary file "c:\Documents and Settings\Darren Birks\My Documents\Visual Studio Projects\Winston\Release\BAT000001.bat" with contents [ @echo off ml /Cp /I. /c /coff /Zi /Fo".\Release"\"Decode".obj "c:\Documents and Settings\Darren Birks\My Documents\Visual Studio Projects\Winston\Code\68000asm\Decode.asm" if errorlevel 1 goto VCReportError goto VCEnd :VCReportError echo Project : error PRJ0019: A tool returned an error code from "Performing Custom Build Step" exit 1 :VCEnd ] Creating command line ""c:\Documents and Settings\Darren Birks\My Documents\Visual Studio Projects\Winston\Release\BAT000001.bat"" 
    Output Window
       
    Performing Custom Build Step Microsoft (R) Macro Assembler Version 7.10.3077 Copyright (C) Microsoft Corporation. All rights reserved. Assembling: and MASM : fatal error A1000: cannot open file : and Project : error PRJ0019: A tool returned an error code from "Performing Custom Build Step" 
    Results
       
    Build log was saved at "file://c:\Documents and Settings\Darren Birks\My Documents\Visual Studio Projects\Winston\Release\BuildLog.htm" WinSTon - 2 error(s), 0 warning(s)

    Could this be related to long filename, if so why no compaint about C:\Documents, which also would be invalid/none existant.

  • Peter Leahy

    Hi Darren,

    Can you paste in the command from the build log, that would show he actual parameters for the invokation of ml.

    Ronald Laeremans
    Visual C++ team

  • jaslegume

    That solved it thanks Big Smile
  • jpursell

    Does cleaning the quotation marks around the parameters to /Fo (making it: ml /Cp /I. /c /coff /Zi /Fo"$(OutDir)\$(InputName).obj" "$(InputPath)") fix the problem

    Thanks,
    Tarek


  • Visual C++ 6 Project with ASM module -> VS2003