| *** zbenjamin is now known as Guest47590 | 02:50 | |
| *** zbenjamin_ is now known as zbenjamin | 02:50 | |
| *** SpeedEvil is now known as Guest89189 | 03:27 | |
| *** frinring_ is now known as frinring | 04:15 | |
| *** BitEvil is now known as SpeedEvil | 05:32 | |
| rubdos | Someone working on getting Rust to work in a more-or-less clean way in sb2? | 10:12 |
|---|---|---|
| rubdos | Last thing I see is http://repo.merproject.org/obs/home:/sfietkonstantin:/sailfish:/rust/sailfishos_armv7hl/ with a DO NOT USE tag | 10:12 |
| rubdos | Running rustup in sb2 seemed to work, but that gives https://gitlab.com/rubdos/whisperfish/-/jobs/340724516 some creepy log messages. | 10:13 |
| Nico[m]1 | While I haven't played around with Rust in combination with Sailfish, I had quite a few bad experience with getting it to work with a musl based OS, so it doesn't really surprise me, that it fails with sb2 ._. | 10:19 |
| rubdos | SFOS uses musl? | 10:19 |
| Nico[m]1 | No, but the sb2 environment uses some kind of libc forwarding | 10:20 |
| rubdos | Ah okay, that's probably why some c related stuff doesn't really play well | 10:20 |
| rubdos | only reason that I need to build it in sb2 is because of the C linkage :-( | 10:20 |
| wdehoog | rubdos: I have build librespot using yocto. | 10:22 |
| wdehoog | in case you are interested: https://github.com/wdehoog/meta-sfos-librespot | 10:22 |
| wdehoog | I only tested the binary briefly. it seemed to work | 10:23 |
| rubdos | woah, people use yocto to build sailfish stuff?! :O | 10:25 |
| rubdos | interesting though | 10:25 |
| Nico[m]1 | LLVM (which rust relies on) also used to have some issues on Sailfish btw: https://kastlunger.blogspot.com/2019/04/lets-do-time-warp-again-or-compile-llvm.html | 10:26 |
| rubdos | ... maybe I should just cross compile on my host system | 10:27 |
| rubdos | this all sounds waaaay to scary :) | 10:27 |
| rubdos | or compile the thing on my phone... | 10:27 |
| rubdos | but that doesn't work with CI | 10:27 |
| rubdos | (is there gitlab-ci for LTE connections?) | 10:28 |
| rubdos | thanks for the links, gonna read them | 10:28 |
| wdehoog | I could not get rust itself build on obs or sb2 so I had no other way. | 10:28 |
| rubdos | wdehoog: rustup on sb2 *seems* to do something, but as soon as you go use scary things (like proc-macro2) it starts to hate you | 10:28 |
| wdehoog | unfortunately meta-rust does not support buidling rust and cargo itself | 10:29 |
| rubdos | I suppose having native Rust as an RPM package would be cleanest indeed... | 10:29 |
| wdehoog | funny this proc-macro2 stuff is also a problem when buidling rust on yocto | 10:29 |
| Nico[m]1 | Well, the proc macro is also the reason you can't actually compile rust with the default musl toolchain... Because it is code that is dynamically loaded and dynamically loaded code isn't supported by the official musl toolchain... | 10:30 |
| rubdos | ^ that's probably the reason I segfault on arm and hang on i486 then | 10:32 |
| rubdos | so native cross-compiling it is | 10:32 |
| rubdos | ... anyone got qtcore and qtmetaobject running in a cross compiler? :D | 10:32 |
| rubdos | Maybe I can link in sb2, but build in a cross compiler? | 10:33 |
| Nico[m]1 | Could you grab a sailfish image and setup a VM? Could be easier ;p | 10:34 |
| rubdos | why use a VM when I have an octa core phone laying around .... | 10:35 |
| Nico[m]1 | Yeah, that works too :D | 10:35 |
| Nico[m]1 | But hard to use in CI | 10:35 |
| rubdos | You're claiming VMs are any easier to use in CI? :D | 10:36 |
| Nico[m]1 | Gitlab CI? Yes, usually | 10:36 |
| rubdos | Maybe I can just grab a raspberry pi 4 and have that compile the thing for armv7 | 10:37 |
| Nico[m]1 | I used them quite extensively at some point | 10:37 |
| Nico[m]1 | Then you still have the problem, that you need to link to the correct C libraries | 10:37 |
| rubdos | ah right | 10:37 |
| rubdos | I need the Qt stuff on Sailfish, not the Qt stuff on Raspberry :( | 10:38 |
| rubdos | I guess I should just write it in C++ then | 10:38 |
| Nico[m]1 | That's what I did :D | 10:38 |
| rubdos | It's how I started, but then I felt the pain of C++ again | 10:38 |
| Nico[m]1 | But you could also try compiling on your phone,and if that works, you can just image your phone and use that as a build VM | 10:39 |
| rubdos | ... and now I feel the pain of getting Rust to work with Qt on a cross target. | 10:39 |
| rubdos | lol, image my phone | 10:39 |
| Nico[m]1 | Or use the Emulator as the build VM | 10:39 |
| rubdos | pretty sure it'd work though | 10:39 |
| rubdos | but then why do I have a threadripper... | 10:39 |
| rubdos | ah right, emulator | 10:40 |
| rubdos | gonna go for lunch now, gotta teach in 1h | 10:40 |
| Nico[m]1 | You could run the VM with 16 cores? | 10:40 |
| Nico[m]1 | Enjoy your meal. I hope there is not too much rust in it ;p | 10:41 |
| rubdos | The annoying part about running it in a VM is the poor integration with SailfishOS SDK | 13:42 |
| rubdos | if I'm doing it in Rust, I at least want the almost out-of-the box experience for contributers.. | 13:42 |
| rubdos | Heh, I don't ge the unimplemented syscalls anymore in SailfishOS 3.2.0.12 platform SDK: https://gitlab.com/rubdos/whisperfish/-/jobs/341033501 | 14:10 |
| rubdos | Nope, still segfaults :) | 14:11 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!