I think that makes the most sense. I have enough memory cards to try both options. Plus it is good for my ADD to be able to try something different after a half hour...
I found on the Qt link: http://doc.qt.io/QtForDeviceCreation/qt ... forms.html
Qt is supported for the Pi 2, but for eLinux. It doesn't mention Windows IoT. This might not matter because Win IoT might be close enough to windows, and it might just work if the Qt libraries needed are compiled into the .exe at the development station. The the app would be sent to the Win IoT with everything needed. I think the bottom line is that I want to try both.
I am a Microsoft fanboy so I am interested in VS 2015 and this new IoT OS anyway.
Making Raspberry Pi Gauges - The Blog
Re: Making Raspberry Pi Gauges - The Blog
I'd be interested in that, too. It's a new thing.
Re: Making Raspberry Pi Gauges - The Blog
More problems...
I got Qt installed on the Pi. Qt 4. I installed the SIP and PyQt4, which took like 3 hours to compile and make.
Then I found out the RoundGauge used in the QML file is QtQuick 2, which requires Qt5. WTF!!!!!
So now, I absolutely need to get Qt5 and QtQuick 2 running on the Pi or the Gauges are out.
I was going to try to convert the code to use Qt4 until I realized that the gauges, which is the whole point of this ridiculous integration requires Qt5.
My new and only real goal for Raspbian is to get Qt5, along with PyQt5 configured on the Pi2 or it is a deal breaker in Raspbian.
I got Qt installed on the Pi. Qt 4. I installed the SIP and PyQt4, which took like 3 hours to compile and make.
Then I found out the RoundGauge used in the QML file is QtQuick 2, which requires Qt5. WTF!!!!!
So now, I absolutely need to get Qt5 and QtQuick 2 running on the Pi or the Gauges are out.
I was going to try to convert the code to use Qt4 until I realized that the gauges, which is the whole point of this ridiculous integration requires Qt5.
My new and only real goal for Raspbian is to get Qt5, along with PyQt5 configured on the Pi2 or it is a deal breaker in Raspbian.
Re: Making Raspberry Pi Gauges - The Blog
Does the Raspbian apt repository not have a pre-compiled Qt5 in it?
Re: Making Raspberry Pi Gauges - The Blog
Also, couldn't you just build it from source? It would be an overnight job, but at least you would have it.
http://wiki.qt.io/Native_Build_of_Qt5_on_a_Raspberry_Pi
http://wiki.qt.io/Native_Build_of_Qt5_on_a_Raspberry_Pi
Re: Making Raspberry Pi Gauges - The Blog
More like over a couple days...Adam wrote:Also, couldn't you just build it from source? It would be an overnight job, but at least you would have it.
http://wiki.qt.io/Native_Build_of_Qt5_on_a_Raspberry_Pi
You may also want to overclock your Pi. I overclocked mine at 900 MHz and it took 38 hours to compile and the temperature was a steady 51 C - 54 C (with case, no heat-sinks, no fans).
Re: Making Raspberry Pi Gauges - The Blog
So, that is correct. there are no apt-get packages officially from Qt yet. I tried another source and added it to the apt/sources, but it failed.
I saw that link, and I have to be totally honest. It seemed like a disaster of a build, and I didn't totally understand the need for an external usb flash drive. For the procedure. I am going to have to go back and really read it. I was hoping at this point to just download a RPi2 image with Qt5 already installed. You would thing that this is a common enough thing, and the procedure is a little intimidating for how many places you can make an error. Then you have to configure, make, and make install PyQt5 after all of this. That procedure for PyQt4 took 3 hours. That was successful for what ever that is worth.
I saw that link, and I have to be totally honest. It seemed like a disaster of a build, and I didn't totally understand the need for an external usb flash drive. For the procedure. I am going to have to go back and really read it. I was hoping at this point to just download a RPi2 image with Qt5 already installed. You would thing that this is a common enough thing, and the procedure is a little intimidating for how many places you can make an error. Then you have to configure, make, and make install PyQt5 after all of this. That procedure for PyQt4 took 3 hours. That was successful for what ever that is worth.
Re: Making Raspberry Pi Gauges - The Blog
gcc can cross-compile for ARM.billgiacheri wrote:So, that is correct. there are no apt-get packages officially from Qt yet. I tried another source and added it to the apt/sources, but it failed.
I saw that link, and I have to be totally honest. It seemed like a disaster of a build, and I didn't totally understand the need for an external usb flash drive. For the procedure. I am going to have to go back and really read it. I was hoping at this point to just download a RPi2 image with Qt5 already installed. You would thing that this is a common enough thing, and the procedure is a little intimidating for how many places you can make an error. Then you have to configure, make, and make install PyQt5 after all of this. That procedure for PyQt4 took 3 hours. That was successful for what ever that is worth.
https://askubuntu.com/questions/250696/ ... le-for-arm
Re: Making Raspberry Pi Gauges - The Blog
So I guess I didn't update the QT stuff. I did compile it on the Pi, It took like a day and a half because it was so slow. Then the rendering of the gauge controls was so terrible, I deemed it unusable because it was barely able to refresh/repaint about once per second. It was bad. My new plan unfortunately is in the other thread, which is to use TK since I found a halfway decent gauge class. The pyobd is in wx though... so I am in the process of looking at all that. I am basically looking to use the pyobd backend imported into my gui file, and have the back end update the gauges.
Unfortunately doing anything on the pi sucks, so I started using Windows. I built the gauges in TK and can set them as shown in the other thread. I couldn't get my laptop to connect though, Then I realized it is trying to connect via /dev/ so it is specifically Linux based, so I loaded it in a Debian VM and installed Wingware Personal, which seems pretty good for python. I got the original pyobd running, but am having issues connecting to the USB -> OBD2 USB interface. I think it is a VM thing... I try to use the USB controller for the VM to enable the USB->OBD interface and it keeps hanging.
My next step is to load the pyobd stuff on the pi and just try it to see if it connects to ensure my connector didn't break as I did get it to work before with a different pyobd fork. I like the front end of the original since it has more features so I am trying to get that working.
Unfortunately doing anything on the pi sucks, so I started using Windows. I built the gauges in TK and can set them as shown in the other thread. I couldn't get my laptop to connect though, Then I realized it is trying to connect via /dev/ so it is specifically Linux based, so I loaded it in a Debian VM and installed Wingware Personal, which seems pretty good for python. I got the original pyobd running, but am having issues connecting to the USB -> OBD2 USB interface. I think it is a VM thing... I try to use the USB controller for the VM to enable the USB->OBD interface and it keeps hanging.
My next step is to load the pyobd stuff on the pi and just try it to see if it connects to ensure my connector didn't break as I did get it to work before with a different pyobd fork. I like the front end of the original since it has more features so I am trying to get that working.