Re: [Nasm-users] [Nasm-devel] SETING PROBLEM OF NASM ON INTEL MACHINE

[Frank K. <fbk...@co...>]

Manu Rastogi, Noida wrote:
> Dear sir/madam ,
> 
> I really need your help . I am trying to build the visual C++ workspace 
> on intel machine . This workspace has  got some x86 assembly files which 
> is to compiled but I am *not* able to compile these assembly file . the 
> error I am getting is as follows
> 
>  
> 
> performing Custom Build Step on ..\blit\blit_mmx.asm
> 
> 'nasm' is not recognized as an internal or external command,
> 
> operable program or batch file.
> 
> Error executing c:\winnt\system32\cmd.exe.
> 
>  
> 
> blit_mmx.obj - 1 error(s), 0 warning(s)
> 
>  
> 
> similarily for other Visual C++ workspace I am getting similar error
> 
>  
> 
> -------------------Configuration: libxvidcore - Win32 
> Debug--------------------
> 
> Assembling ...\..\src\utils\x86_asm\mem_transfer_mmx.asm
> 
> 'nasm' is not recognized as an internal or external command,
> 
> operable program or batch file.
> 
> Error executing c:\winnt\system32\cmd.exe.
> 
>  
> 
> xvidcore.dll - 1 error(s), 0 warning(s)
> 
>  
> 
> please help me in this regard at your earnest.

Hi Manu,

I'm transferring your query from the "nasm-devel" list to the 
"nasm-users" list, since this doesn't seem to be a "Nasm problem".

I'm not familiar with Visual C++, or with modern Windows versions, but 
it sounds as if Nasm isn't on your path. One thought: the Windows build 
of Nasm is usually named "nasmw.exe" (for no good reason?). If VC++ is 
looking for "nasm.exe", this could be a problem. Either renaming 
"nasmw.exe" to "nasm.exe" or telling VC++ "nasmw" should fix that 
problem. You may need to put the directory where nasm/nasmw resides on 
your path, or perhaps giving VC++ the full path to nasm(w) would do it.

Maybe some VC++/nasm user can provide better suggestions.

Best,
Frank