Common questions #17
Comments
|
Could you inform me of your environment (like OS, cmake and clang version)? It seems the version of clang is a little bit old. |
|
@HidenoriMatsubayashi 💪 Building with sound null safety 💪 Building an eLinux application with wayland backend in release mode for arm64 target... 17.4s CMake Error at /opt/abc-wayland/sysroots/x86_64-abcsdk-linux/usr/share/cmake-3.16/Modules/CMakeTestCXXCompiler.cmake:53 (message): could you help me in fixing it? my flutter-elinux doctor says regsrds |
|
@Nagendra-Bankupalli You try to cross-compile, right? If so, please see https://github.com/sony/flutter-elinux/wiki/Building-flutter-apps#2-cross-building-from-x64-to-arm64 |
|
@HidenoriMatsubayashi , |
|
I understood. Is it possible to try the build by specifying only your sysroot without using the Yocto SDK's toolchain? It means $ flutter-elinux build elinux --target-arch=arm64 --target-sysroot=<absolute_path_to_yocto_sdk_sysroot> |
|
@HidenoriMatsubayashi , below is the error Building an eLinux application with wayland backend in release mode for arm64 target... 17.5s CMake Error at /usr/share/cmake-3.16/Modules/CMakeTestCXXCompiler.cmake:53 (message): is not able to compile a simple test program. |
|
Thanks. Can you pass self-build? $ flutter-elinux build elinux |
|
It works for x64 target (weston) and I can even run profile (dev tool) as well. |
|
Did you install required tools to cross-build? $ sudo apt install gcc-aarch64-linux-gnu g++-aarch64-linux-gnu
$ sudo apt install libstdc++-8-dev-arm64-cross |
|
No, I thought target tool chain would be sufficient , will try and let you know |
|
Yes, we need these tools to cross-build when we use host's toolchain (clang/llvm). |
|
@HidenoriMatsubayashi , thank you for the inputs, on profiling, I have updated .flutter_custom_devices.json with all required info about my target |
|
Sounds good.
"runDebug": [
"ssh", "user@192.168.0.100", "/tmp/${appName}/${appName} -b ."
],
"forwardPort": [
"ssh", "-o", "ExitOnForwardFailure=yes",
"-L", "127.0.0.1:${hostPort}:127.0.0.1:${devicePort}", "user@192.168.0.100"
],
"forwardPortSuccessRegex": "Linux" |
|
Yes, forwardPort and forwardPortSuccessRegex have been added to my flutter_custom_devices.json below commands can be used to install and uninstall app from the target Tried running app on target and shows below line, does this means we can observe it on host, if portForward is success, if yes please let me know how to do it? am I missing something ? |
|
Could you inform me of your trying command and error messages? |
|
with below commands I could get observatory data on host chrome from target (my-device) target : open chrome on host "http://127.0.0.1:34549/CA1Zk5rr-LQ=/"
|
|
Yes, Internal steps:
|
|
Yes,I expected the same, but the command did not provide any log (app runs on target successfully), so I tried it manually , it worked ` |
|
In my environment, it works fine. $ flutter-elinux run -d raspberry-pi4
Launching lib/main.dart on eLinux in debug mode...
Uninstall sample from raspberry-pi4.
hidenori@192.168.0.10's password:
Uninstallation Success
Install sample (build/elinux/arm64/debug/bundle) to raspberry-pi4
hidenori@192.168.0.10's password:
Installation Success
Launch sample.name on raspberry-pi4
hidenori@192.168.0.10's password:
hidenori@192.168.0.10's password:
Syncing files to device eLinux... 202ms
Flutter run key commands.
r Hot reload. 🔥🔥🔥
R Hot restart.
h List all available interactive commands.
d Detach (terminate "flutter run" but leave application running).
c Clear the screen
q Quit (terminate the application on the device).
💪 Running with sound null safety 💪
An Observatory debugger and profiler on eLinux is available at: http://127.0.0.1:43237/xd6sW5hdEoE=/
Activating Dart DevTools... 1,830ms
The Flutter DevTools debugger and profiler on eLinux is available at:
http://127.0.0.1:9100?uri=http://127.0.0.1:43237/xd6sW5hdEoE=/I couldn't reproduce this issue. So, could you do debugging by adding log messages to around https://github.com/sony/flutter-elinux/blob/main/lib/elinux_device.dart#L141?
Why do you want to use profile mode? I think debug mode is well enough. The difference between debug and profile mode is that debug mode is debugging + profiling, whereas profile mode is profiling only. |
I added it just now. #34 |
|
I can reproduce the same issue using i.mx8m device, but if I use raspberry-pi4, it's no problem. So, it looks depending on the target device or environment. |
|
Thanks for updating, Yes mine is similar platform, the below line of code is blocked. below line could be issue? (protocol_discovery.dart +152) |
|
@HidenoriMatsubayashi , Have you tried flutter-gallery app on embedded target ? |
|
Yes, I have. It worked fine. |
|
@HidenoriMatsubayashi , |
|
Proverbially, I guess you haven't set |
|
@HidenoriMatsubayashi , thank you it works. |
|
Hi,I created a flutter custom device, but when I entered the command "flutter-elinux devices" I found that instead of one device, two sailfish-devices are displayed. Because of this, when I enter the command "flutter-elinux run -d sailfish-device", debugging does not work correctly for me. What could this |
|
@Rustam-Askerov |
|
I run virtualbox on my pc and as a custom device I use a virtual machine on which sailfish os is installed. In the instructions for the Sailfish SDK, it says ssh |
|
Also I tried to build the app from x64 host for arm64 using cross compilation but when compilation reaches 100% the error appears:
|
|
But libxkbcommon0 library is installed: |
|
hi, no flutter hot load |
How can we setup for activating Dart DevTools on your RPi board? |
hi,
The text was updated successfully, but these errors were encountered: