Edited by
Alex Baines
on
Reason: architecture clarification
I believe the Linux 4coder port should already compile for 32-bit x86 (and probably ARM, but I haven't tested); for the Pi it might additionally require an OpenGL ES renderer though.
I'd be willing to help get that up and running if Allen wants.
I have a Pi and I've been wanting to get 4coder on it, but I don't think the time is right for it yet. It should not be too long but right now the big priorities are:
1. Full Unicode Support
2. Custom API Overhaul - Alternate editing paradigms, custom DLL reloading
3. Platform Layer Revision - Easier for porting to Mac, more modular rendering system, more features in the thread pool
4. Custom GUIs
5. ... event horizon past which I have no plans ...
Those are pretty broad todo items, but the chance of getting a Pi port ready to go by May or June this year seems pretty high to me.
I was thinking about it recently. I cleaned up the renderer so if I need a separate OpenGL ES renderer it shouldn't be too hard to support... which means yes. :)
Oh what do you know? I had trouble with it for some reason when I spent about one day on it a while back. But I'll take a look at it soon (maybe not this month though) and straighten it out. Thanks for the tip Martins.
Sorry for the thread necromancy, found this with search.
Is there still an appetite for a 4coder build on Raspbian? I recently got my hands on a Raspberry Pi 4 and I've really been enjoying it as a development desktop. I'd enjoy it even more with 4coder!
I am still interested in getting 4coder on the raspberry pi. I also still have a lot of other important things to do in 4coder. It'll happen eventually, for now I am noting that there is still interest in it.