'nmake' is not recognized as an internal or external command

Command Line build steps failing 'nmake' is not recognized as an internal or external command

Hello,

I have my .bat files calling Microsoft Visual Studio 'nmake' as below 

```
echo off

rem AVX2

nmake -f Makefile.AVX2.w64 clean

nmake -f Makefile.AVX2.w64 vAVX2

nmake -f Makefile.AVX2.w64 clean
```

but Team City errors with 

"'nmake' is not recognized as an internal or external command"

when doing it by hand, I run the .bat from Microsoft Developer Studio x64 Native Tools Command Prompt, which has a lot of definitions, etc., the .bat it does not work for me either if I run it from an ordinary Command Prompt.

Is there a way to tell Team City to run the .bat from x64 Native Tools Command Prompt?

If not would you know how can I, from within ordinary Command Prompt, somehow call x64 Native Tools Command Prompt, and then execute the commands within it?

I am new to Team City, so may I ask another question, please, the .bat normally generates an .exe, which I would like to treat as an artefact, could you direct me please to instructions on how to specify what to Zip, etc.? 

Thanks. 

Regards,
Robert

1 comment
Comment actions Permalink

P.S.

Here is the answer on "how can I, from within ordinary Command Prompt, somehow call x64 Native Tools Command Prompt, and then execute the commands within it", and I think that I shall be able to make it work like that, etc.

Use the Microsoft C++ toolset from the command line | Microsoft Docs

May I ask if it runs, on the machine where the build agent runs, in my case is the same where the TC server runs, i.e., I am using Free Professional server license, from an ordinary Command Prompt, will it run from Team City, as Command Line build, using my .bat?

Thanks.

0

Please sign in to leave a comment.