Jack Jansen <Jack.Jansen@oratrix.com> writes: > I like the idea, but I think it could be implemented slightly cleaner > (without need for the make clean and all the environment variables). I > was thinking something along the lines of having two build > subdirectories (as is already supported currently), let's say > build-host and build-crosscompile. I think requiring the host compilation is wrong in the first place. Instead, when cross-compiling, Python should require that the host python already exists - whether from a previous configure;make; make install, or because a host Python had been there all along (it doesn't even have to be the same Python version). Likewise, building the host pgen in a cross-compilation should not be necessary, since the pgen output is shipped with the source release. configure already supports cross-compilation, so setting CC should not be necessary (since it will automatically find arm-linux-gcc if you have a GNU cross-compilation environment). I don't volunteer to write patches, either, but I do volunteer to review patches. Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4