Code: Select all
Parsing ...Illegal character '#' (character code 0x23) at "MMT.pnml", line 32, column 1
I'm using the following code:
What am I doing wrong and how can I fix it so that I can compile this?
Moderator: Graphics Moderators
Code: Select all
Parsing ...Illegal character '#' (character code 0x23) at "MMT.pnml", line 32, column 1
Code: Select all
echo "[CPP] ogfx-industries.nml"
cc -D REPO_REVISION=5518 -D NEWGRF_VERSION=5518 -C -E -nostdinc -x c-header -o ogfx-industries.nml ogfx-industries.pnml
echo "[LNG] custom_tags.txt"
echo "VERSION :v5518M (bb833d0eaca4)" > custom_tags.txt
echo "VERSION_STRING :v5518M (bb833d0eaca4)" >> custom_tags.txt
echo "TITLE :OpenGFX+ Industries v5518M (bb833d0eaca4)" >> custom_tags.txt
echo "FILENAME :ogfx-industries.grf" >> custom_tags.txt
echo "REPO_HASH :bb833d0eaca4" >> custom_tags.txt
echo "NEWGRF_VERSION :5518" >> custom_tags.txt
echo "[NML] ogfx-industries.grf"
"~/bin/nmlc" -c --grf ogfx-industries.grf ogfx-industries.nml
echo "[BUNDLE] ogfx-industries"
if [ -e ogfx-industries ]; then rm -rf ogfx-industries; fi
mkdir ogfx-industries
for i in ogfx-industries.grf docs/readme.txt docs/license.txt docs/changelog.txt; do cp -rf $i ogfx-industries; done
echo "[BUNDLE TAR] ogfx-industries.tar"
"/usr/bin/tar" -cf ogfx-industries.tar ogfx-industries
So, I followed it completely, and the test commands all work.Transportman wrote:I once wrote a guide to set up a compile environment on Windows (as make and other commands are Linux commands).
Code: Select all
E:\Games\NMLstuffs\Modern Maglev Trains>make
[CPP] MMT.nml
/bin/bash: cc: command not found
make: *** [MMT.nml] Error 127
Code: Select all
PATH="/e/MinGW/msys/1.0/bin:/e/MinGW/bin:/e/Games/NMLstuffs/Modern Maglev Trains:/c/Python27:$PATH"
Code: Select all
PATH="/e/MinGW/msys/1.0/bin:$PATH"
The cc command is unfortunately absent.Alberth wrote:You started a new bash after changing the .bashrc? The file gets read only when you start a new shell, thus making a change in that file does not affect any shell that is already running.
Make just invokes the programs at the standard path, so you can easily test by asking online help or a version to the cc program, like "cc --version"
Is there a cc command in that directory?
Can you run it yourself? ("/e/MinGW/msys/1.0/bin/cc --help" or so)
home dir creation should not be a problem.
Shameless plug. Here's my version that uses cygwin.Transportman wrote:I once wrote a guide to set up a compile environment on Windows (as make and other commands are Linux commands).
Yes, I've checked and double-checked.Transportman wrote:Are you sure your Python path is correct? It is the only one that would be on the C drive according to your path.
The CC command is the mingw's synonym for gcc (or cpp). It needs to be in the search path as available in MinGW shell. Besides NML you also need GCC in order to build the project.Erato wrote:The cc command is unfortunately absent.Alberth wrote:You started a new bash after changing the .bashrc? The file gets read only when you start a new shell, thus making a change in that file does not affect any shell that is already running.
Make just invokes the programs at the standard path, so you can easily test by asking online help or a version to the cc program, like "cc --version"
Is there a cc command in that directory?
Can you run it yourself? ("/e/MinGW/msys/1.0/bin/cc --help" or so)
home dir creation should not be a problem.
Sylf wrote:Shameless plug. Here's my version that uses cygwin.Transportman wrote:I once wrote a guide to set up a compile environment on Windows (as make and other commands are Linux commands).
That sounds nice, one long compilation the first time, only a few minutes for every time after that. I would be interested to know how it would compare with my guide, maybe something to test one day.Hopefully, you will be presented with a working YETI.tar after a few hours. It takes about 3 hours on my PC the very first time I compile YETI. After that, it's about a 2 minute job.
Okay, and your NML is really installed in e/Games/NMLstuffs/Modern Maglev Trains? Because I would suspect that that contains only the code of your NewGRF, and that NML itself is installed somewhere else.Erato wrote:Yes, I've checked and double-checked.Transportman wrote:Are you sure your Python path is correct? It is the only one that would be on the C drive according to your path.
This.3iff wrote:I use mingw and bounced into the same problem with CC. I found adding the following line (before CC is used/called for the first time) fixes the problem.
CC = gcc
Hopefully, that will work for you too.
Users browsing this forum: No registered users and 7 guests