Hey, nicolapcweek94 
I was able to build the latest GNU Emacs directly on the PinePhone's CPU, including the pure GTK and native elisp compilation features. I had to limit the build to two parallel jobs (more than 2 caused OOM crashes). It took ~2h:36m, CPU utilization was around 50% and the temperatures stabilized at constant 60°C on the CPU and 56°C on the GPU.
After this experience, I have become interested in cross-compilation as well, although I have very little experience with it.
Not me. I track the Emacs source code commit-by-commit; I'd never give up this control for any amount of convenience.
However, if you have it already figured out, please do share your method and observations.
I was able to build the latest GNU Emacs directly on the PinePhone's CPU, including the pure GTK and native elisp compilation features. I had to limit the build to two parallel jobs (more than 2 caused OOM crashes). It took ~2h:36m, CPU utilization was around 50% and the temperatures stabilized at constant 60°C on the CPU and 56°C on the GPU.
After this experience, I have become interested in cross-compilation as well, although I have very little experience with it.
Quote:I'm also looking to setup the whole thing as a repo with a weekly or daily build job, if the repo setup doesn't require too much maintenance, which I'd gladly share if anyone's interested.
Not me. I track the Emacs source code commit-by-commit; I'd never give up this control for any amount of convenience.
However, if you have it already figured out, please do share your method and observations.