feat: Implement experimental elinux support

[Losses]

This pull request introduces experimental eLinux support to Rinf. While there are still some modifications needed on the Flutter-eLinux side, I have initiated a discussion on this issue: Issue #270.

Given the stringent performance requirements of embedded environments, the performance advantages of Rust can significantly benefit embedded development.

[temeddix]

Thank you very much for the PR :)

Actually, Cargokit is not a Rinf product. Cargokit is maintained as a separated project by @irondash.

• https://github.com/irondash/cargokit

Rinf simply uses Git subtree to use Cargokit as part of the package. What do you think about creating a PR at Cargokit? I will be able to include the new changes in Rinf as soon as it gets merged over there.

[Losses]

Sure :P

[temeddix]

I've also created a PR at Cargokit to assist with the process

• Use flutter test in CI irondash/cargokit#80

[Losses]

I've also created a PR at Cargokit to assist with the process

* [Use `flutter test` in CI irondash/cargokit#80](https://github.com/irondash/cargokit/pull/80)

Thank you!

[temeddix]

Hi @Losses,

I think we can bypass the upstream branch from Cargokit and add this functionality directly on our side, as there's an issue with the review duration over there. Would this PR still be helpful? If so, I'd be happy to publish a new version with it.

[Losses]

@temeddix Yeah! Why not!

[temeddix]

@Losses I'm not very familiar with Flutter-ELinux ecosystem, so please pardon me if I miss something. It would be greatly appreciated if we can share some more information together.

• This PR seems to be related to flutter-elinux, right? If we merge this PR and publish a new version, would it work directly with flutter-elinux?
• Would this change affect normal Flutter apps?
• Does flutter-elinux use the elinux/CMakeLists.txt file inside a Flutter plugin, as the build entry?
• Have you tested on a physical device? Also, what device would you recommend me and other devs to test on, maybe a Raspberry Pi with a small display?

P.S. I've been watching your great work on the music player Rune. If you need any help upgrading to Rinf 8, please let me know :)

[Losses]

@temeddix

would it work directly with flutter-elinux?

I think the answer is yes, I made a PR for flutter-elinux to fix the compatibility with rinf

Would this change affect normal Flutter apps?

Absolutely not

Does flutter-elinux use the elinux/CMakeLists.txt file

I think this is no much difference with normal flutter projects, but it‘s worth to check the source code.

Have you tested on a physical device?

I've only tested on a x86 machine and it compiled successfully. Cross compiling is sheltered since the compiling pipeline of a library I use was broken, but they fixed it several weeks ago. I think I could embark the support of elinux again these days.

Raspberry Pi with a small display is enough for testing.

upgrading to Rinf 8

Thanks! But Rune relies on protobuf for the remote control protocol to cover the situation where the UI and Rust logic are not on the same device. If Rinf 8 does not cover this use case, maybe we cannot upgrade it for now. Sad story.

[temeddix]

Thank you for the detailed reply.

I have one last question: We will add eLinux as the experimental platform to the readme files right after this PR gets merged. Could you accompany us on a journey of making it stable, just like other platforms, if you're okay?

[Losses]

@temeddix

Thank you for considering adding eLinux as an experimental platform to the readme files! I'd be happy to help make eLinux support stable alongside the other platforms, within the constraints of my available time.
If developers encounter any issues or have questions related to eLinux integration once Rune introduces this support, I'm willing to collaborate on troubleshooting and finding solutions. I appreciate you reaching out about this, and I look forward to contributing to the stability of the eLinux platform support when possible.

[temeddix]

Thanks! Let's keep in touch.