I have been trying to build Luaplayer from the source for a while now, to get an insight into how to make standalone apps. I believe I've sorted all the dependencies...however, when I do "make", I get hit with a string of errors...:
Probably related to this is the error I get when trying to compile the sample app:
I don't know if this is the problem you are having, but if you are using GCC on a Windows machine, you have to be careful about preserving the case of filenames. Some legacy DOS applications convert filenames into upper case, and Windows will still treat the filenames the same. However, many of the Linux tools require that the original case of the filename be preserved.
I ran across this issue when I was building sample applications from the PSPSDK. I was getting an error something like:
It turns out that the culprit was an old tool I had written about 10 years ago to convert Unix/Linux linefeeds into evil MS-DOS carriage return+linefeeds to keep my editor happy. It renamed "main.c" to MAIN.C" and broke the build.
Elxx wrote:I have been trying to build Luaplayer from the source for a while now, to get an insight into how to make standalone apps. I believe I've sorted all the dependencies...however, when I do "make", I get hit with a string of errors...:
Looks like you didn't compile Lua from SVN with "make -f Makefile.psp" and "make -f Makefile.psp install".
Elxx wrote:
Probably related to this is the error I get when trying to compile the sample app:
No, this is a documentation bug, take a look at the Makefile.psp-standlone, you need release10 and release15 as the target name.
Elxx wrote:I have been trying to build Luaplayer from the source for a while now, to get an insight into how to make standalone apps. I believe I've sorted all the dependencies...however, when I do "make", I get hit with a string of errors...:
Looks like you didn't compile Lua from SVN with "make -f Makefile.psp" and "make -f Makefile.psp install".
I just tried it again, re-making and re-installing Lua and I still get the same errors.
If you have any questions, please write which step fails and post the output of the failure as text (then it is easier for others to find it by using the forum search function). Most of the time the beginning of the output is more interesting than the end, e.g. "library foo not found" is more informative than a page of "undefined references".