Open rogerjames99 opened 2 years ago
I am now totally confused about the cross compilation environment. From going through the verbose logs from mix firmware I can see things are being cross compiled using a sysroot hidden below the .nerves directory in my home directory. So the qt5 stuff on my system should be irrelevant. Is this something to do with erlang and rebar? Do they do some magic to mimic the hosts build environment in the targets sysroot?
I am now totally confused about the cross compilation environment. From going through the verbose logs from mix firmware I can see the logs are being cross compiled using a sysroot hidden below the .nerves directory in my home directory. So the qt5 stuff on my system should be irrelevant. Is this something to do erlang and rebar? Do they do dome magic to mimic the hosts build environment in the targets sysroot?
That's the Nerves cross compilation build setup. It downloads and sets up a Buildroot build environment under the covers. That part is mostly ok looking.
Your logs look alright as well (I never figured out how to set the background color on the new QML setup).
The white screen means it's actually starting QT web engine, but it's not loading a website. You'd need to add networking to your Nerves image and then call the "goto url" function in web_kiosk.
I really need to get some new glasses! I think you guessed what I was saying. It should have said.
I can see from the logs that things are being cross compiled...
Is there a video of your session at NervesCon available anywhere?
Is this stuff documented anywhere? All I can find is a few lines in the getting started document under "Compiling non BEAM code".
I was expecting to see the index.html from the priv resources loaded by default 😞 .
Jaremy,
When I build from my fork I get a white screen on boot. I have made a small change mix .exs to pull webengine_kiosk from your github repo rather than the local filesystem.
I get the following messages in Ringlogger
It looks like something is wrong in my QT environment. The following is the gory details of the qt5 installation on my build system.
Am I correct in my assumption the my host system qt5 installation is been used to provide templates for the qmake cross compilation process being run on the host when the firmware is built?
Any ideas?
Roger