Open GoogleCodeExporter opened 9 years ago
after further investigation of the compiling log. I noticed that after where it
says "process_begin:" its trying to run pspgz.py with a path that uses
backslashes "\" instead of forward slashes "/" so its not finding pspgzp.py. so
i tried running the script where it left off and compressed vshctrl.prx manualy
using pspgz.py and it worked. so i wrote a script to compress all the files
that were being compressed directly after build time and put the script to run
after the Live-system Components which worked fine. then when the compiler
moved to the PXE executables and it was gonna run creat_module_include.py and
ran in the same error as before
Original comment by lilmnm616@gmail.com
on 4 Aug 2012 at 11:32
I have found the problem and fixed it and am including my fix and readme. but
first here is an explanation or at least what i think is happening. When the
makefile calls the pspgz.py or create_module_include.py scripts and trys to
find and run it but falls to find it and returns an error 2 error which means
make couldnt find the *py file and run it. the reason is that when it gets
called the path is converted to a posix or Windows path format (i.e.
C:\cygwin\home\...) but the backslashes are removed so make looks for the *.py
file in a folder that is named the whole path that was stated, but can't as the
folder doesn't exist.
Please read the README.txt with in the zip included on how to use the patch and
some troubleshooting if it doesn't work
Original comment by lilmnm616@gmail.com
on 7 Aug 2012 at 1:26
Attachments:
Original issue reported on code.google.com by
lilmnm616@gmail.com
on 3 Aug 2012 at 1:30