New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ubuntu touch support #19
Comments
Hi, could you perhaps provide the example that is not working? |
It's the readme example.
Yeah, I will try to install Qt debug packages, although I'm not sure if that will work. UPDATE:
|
Now I've got a better trace:
Thanks to @hummlbach for linking me to those debug packages! |
What hardware platform is this running on? |
This is running on a Nexus 5 ( |
Maybe that's because it is cross compiling to a 32 bit architecture from a 64 bit host, and the cfg test in
|
Good idea, I will remove the attributes and the lines for 64-bit to check that. |
Wow, great catch <3 Looks like that's it! |
In the proc_macro cfg(target_pointer_width) has the value of the host, not the target. So instead, generate the string data for both the 32 and 64 bit, but have the generated code select based on target_pointer_width. This is not ideal from a compilation time point of view. Better suggestions welcome. #19
Yes, that's rust-lang/rust#42587 |
I can confirm that it works. Thanks a lot @ogoffart! |
i uploaded 0.0.5 to crates.io |
Hey, first of all: thanks for this awesome project.
I was trying to get this running on Ubuntu touch and I got it working partly. That means that I can get an example to compile and make it start an application window using only Rust, QML and qmetaobject-rs. This works.
Unfortunately though, the application segfaults as soon as I try to export a QObject to QML including a
qt_method
,qt_property
, orqt_signal
.Note that the call to
qml_register_type
and exporting an empty QObject without aqt_method
don't lead to a crash.I'm running the example from the readme.
gdb
backtrace:Using Rust nightly and the system allocator instead of jemalloc:
Given those symptoms, do you have an idea what could go wrong, or what I could do to debug this issue further? Thanks a lot for any hints!
The text was updated successfully, but these errors were encountered: