Thank you all for your input!
I am afraid it will stay some more time in the unbuildable state, as confirmed by a FP-employee here:
https://forum.fairphone.com/t/fairphone-5-source-code-release/99616/15:
Thanks for you patience, unfortunately it will still take some time for us to wrap up this topic properly, say Q2-Q3 2024.
To clarify things, the currently published source tree is as complete as it gets, we published everything we legally can, everything that’s not proprietary in some way. The major change we’ll need to do is to restructure the source tree in a way that it can be built without proprietary dependencies (toolchains, headers, etc), and move those proprietary components into a blobs package, as we’re doing for the previous devices already. This is complex, because the source tree as it comes from suppliers is typically not set up in a way designed for open sourcing.
@dimac4455 thank you for the link to your getting started guide. I already had a look at it, but at first sight I couldn’t figure out if there are A13-specific things in it, and as @mal confirmed, there are some pieces missing for A13 in the HADK. Could you give me a hint which things were done differently to the HADK?
Thank you for this suggestion! I am not familiar with this route (I saw the post by @piggz, but due to no example like in the HADK I don’t feel able to estimate what effort this would take). Could you give me a link for reading something that I could make myself familiar with this approach? I didn’t find anything, but maybe I searched for the wrong things…
You are right, but I wanted to share my thoughts and findings here first and get some feedback, as I wanted to be able to ask the right questions on the porter’s channel But if I decide for trying, I will go there and ask my questions.