Code: Select all
'make' is not recognized as an internal or external command,
operable program or batch file.
What could be the cause of this?
Moderator: Graphics Moderators
Code: Select all
'make' is not recognized as an internal or external command,
operable program or batch file.
Could you elaborate on this answer?planetmaker wrote:you need to install make
Could you describe your setup? It sounds like you are using Windows, while make is a Linux-program, which means you either should have something like Cygwin or MinGW/MSYS to have the make program available, or use the Windows Subsystem for Linux on Windows 10 (but then you would be running an actual Bash-shell).Erato wrote:Around October last year, I last used the make command using the exact setup that I have now. It worked back then, but now, I get this message instead:I tried reinstalling nml, I tried reinstalling Makefile. I tried using commands like "Makefile" instead of "make", but alas, 'twas not to be.Code: Select all
'make' is not recognized as an internal or external command, operable program or batch file.
What could be the cause of this?
I am using Windows 10, Python 2.7.11. As far as I know, I do not have Cygwin, MinGW or MSYS. I am using cmd to run make and to compile the resulting nml file.Transportman wrote:Could you describe your setup? It sounds like you are using Windows, while make is a Linux-program, which means you either should have something like Cygwin or MinGW/MSYS to have the make program available, or use the Windows Subsystem for Linux on Windows 10 (but then you would be running an actual Bash-shell).
This suggests that the issue lies not in Erato's set up but rather lies in the code he wants to compile.Erato wrote:This exact setup has been used a few months prior to successfully call the make command.
In that case: by all means, please check for any flaws in my code that would cause make to be not recognised.wallyweb wrote:This suggests that the issue lies not in Erato's set up but rather lies in the code he wants to compile.Erato wrote:This exact setup has been used a few months prior to successfully call the make command.
make is not a standard Windows command, so if it was working before, you have had to set that up yourself. Did you follow a guide back then?Erato wrote:I am using Windows 10, Python 2.7.11. As far as I know, I do not have Cygwin, MinGW or MSYS. I am using cmd to run make and to compile the resulting nml file.Transportman wrote:Could you describe your setup? It sounds like you are using Windows, while make is a Linux-program, which means you either should have something like Cygwin or MinGW/MSYS to have the make program available, or use the Windows Subsystem for Linux on Windows 10 (but then you would be running an actual Bash-shell).
This exact setup has been used a few months prior to successfully call the make command.
It is in the set up, as not recognizing a command is not a code issue, but the system not being able to find the program it should execute to compile that code.wallyweb wrote:This suggests that the issue lies not in Erato's set up but rather lies in the code he wants to compile.Erato wrote:This exact setup has been used a few months prior to successfully call the make command.
I did follow a guide. IIRC. It's the whole reason I have Python after all.Transportman wrote:make is not a standard Windows command, so if it was working before, you have had to set that up yourself. Did you follow a guide back then?Erato wrote:I am using Windows 10, Python 2.7.11. As far as I know, I do not have Cygwin, MinGW or MSYS. I am using cmd to run make and to compile the resulting nml file.Transportman wrote:Could you describe your setup? It sounds like you are using Windows, while make is a Linux-program, which means you either should have something like Cygwin or MinGW/MSYS to have the make program available, or use the Windows Subsystem for Linux on Windows 10 (but then you would be running an actual Bash-shell).
This exact setup has been used a few months prior to successfully call the make command.
That's what I thought as well.Transportman wrote:It is in the set up, as not recognizing a command is not a code issue, but the system not being able to find the program it should execute to compile that code.wallyweb wrote:Erato wrote:This exact setup has been used a few months prior to successfully call the make command.
This suggests that the issue lies not in Erato's set up but rather lies in the code he wants to compile.
Thanks a lot! This finally works. Well... make now works like a charm. Nml broke tho :\Transportman wrote:Compiling NML and using make is not the same. Make does several things depending on the makefile used, and compiling your NML is one of those things, and generating the .nml file from .pnml files can also be a step in it (and that generated file is then compiled into a GRF).
But if you did follow the guide you linked to, you should also have MinGW and MSYS (which provide the make command to Windows). But I would suggest, since you are using Windows 10 (and I assume it is up to date and 64bits), to follow this guide to set up a new environment. I have got much faster compile times with it.
You're right; it's 0.2.4. I thought I had used version 0.4.4Transportman wrote:Which version of NML do you have? It sounds like you got an ancient version like 0.2.x. You can check with nmlc --version.
That depends on your system. If you are on pure Windows, it would simply be extracting the latest version from the DevZone, if you are running Linux (or the Linux commandline inside Windows), you will need to install it using python and the setup.py file that is in the download.Erato wrote:You're right; it's 0.2.4. I thought I had used version 0.4.4Transportman wrote:Which version of NML do you have? It sounds like you got an ancient version like 0.2.x. You can check with nmlc --version.
Reinstalling nml will reinstall 0.2.4 again. How would I go about installing 0.4.4?
Achso. I got it fixed. I don't know what changed. 12th time's the charm, I guess.Transportman wrote:That depends on your system. If you are on pure Windows, it would simply be extracting the latest version from the DevZone, if you are running Linux (or the Linux commandline inside Windows), you will need to install it using python and the setup.py file that is in the download.Erato wrote:You're right; it's 0.2.4. I thought I had used version 0.4.4Transportman wrote:Which version of NML do you have? It sounds like you got an ancient version like 0.2.x. You can check with nmlc --version.
Reinstalling nml will reinstall 0.2.4 again. How would I go about installing 0.4.4?
Users browsing this forum: No registered users and 14 guests