<boshtannik>
did as it was said until update - got again `unable to fetch ... - hash mismatch`
<boshtannik>
hmm
<boshtannik>
maybe because of date?
<Wizzup>
I don't think so, but yeah. I wonder if something is up with the vbox networking
<boshtannik>
datetime is up to date
<boshtannik>
but it pings 8.8.8.8
<boshtannik>
ohh. just done update
<boshtannik>
again hashes mismatch
<boshtannik>
run upgrade with --fix-missing
<boshtannik>
in parallel, on my actual device recompilinbg kivy from source with KIVY_..._PLATFORM set to 'rpi'
<boshtannik>
(it failed previous time, as on the forume is said, that it is known failure for 32 bit armv7 a8) . In hope to at least achieve same point, where i did fail prev time
<boshtannik>
did someone tried by modifying device tree, to be set to more than 600 mhz - to overclock CPU?
<Wizzup>
I missed why you're compiling kivi, it is not in repos, or?
<boshtannik>
after installing it from repos, it still complain, that it is not compiled.
<boshtannik>
on official website - it is advised to install it via downloadable script
<boshtannik>
which downloads all dependencies, build them, and on top of them - installs kivy.
<Wizzup>
what did you install from the repo and what complains?
<Wizzup>
maemo leste is just debian/devuan
<Wizzup>
so whatever works there should work on maemo leste
<Wizzup>
and mostly vice versa :)
<boshtannik>
it did not work.
<boshtannik>
also kivy heavily rely on opengl, sdl, cpython
<boshtannik>
to run as native gui speed
<boshtannik>
i just wanted to get some experience in writing kivy. It is not interesting to write regular apps onto my regular pc. It seems for me more interesting write, and run on n900 directly - it might help me get more experience in writing guis for embedding systems
<boshtannik>
i guess, there is the ton of similarity with kivy for rpi (raspberry pi zero i guess)
<boshtannik>
(it did not work.) - at least i have tried on previous leste distributive.
<boshtannik>
After switch to new distributive, regular apt-get intall python3-kivy python-kivy-examples - did not help
<boshtannik>
also creating venv - to install kivy lib directly there, also did not help
<boshtannik>
i guess that was segmentation fault, while running hello world app on installed kivy library (during initialization kivy)
pere has quit [Ping timeout: 240 seconds]
<boshtannik>
Now it donwloads all dependencies for SDL2_image, on which i got fail for previous time
<freemangordon>
boshtannik: you will *not* get opengl on N900
<freemangordon>
no matter what you do
<freemangordon>
also, there is no point to compile libs that will remain on your devices only if you plan to make application to be used for everyone
<freemangordon>
later on I will install kivy and examples on my d4, to see what does not work
<boshtannik>
Ohhh. I would be very glad.
<Wizzup>
there is the gl shim I guess, but yeah
<boshtannik>
I try now to find documentation about kivy, supportable window backends to draw graphics.
<boshtannik>
It was pygame, butnow i guess it is deprecated.
<boshtannik>
then it was sdl2, egl, or opengl i do not remember
<boshtannik>
it was possible by set KIVY_WINDOW=SDL2 python3 main.py or whatever, during app start
<boshtannik>
on my virtualbox machine 'sudo apt-get upgrade --fix-missing' thrown "Sub-process /usr/bin/dpkg received a segmentation fault" So i'am not able to install kivy on it.
<sicelo>
why kivy btw? you could use qt with python
<sicelo>
and yes, n900 can be overclocked on linux mainline
<boshtannik>
because of the license
pere has joined #maemo-leste
uvos__ has joined #maemo-leste
<sicelo>
license?
<boshtannik>
kivy lets develop for free, even raise money with it. The company which i was working in, had troubles with qt, because of the specific license, because of use QT for c++ in embedded device.
<boshtannik>
so yes, license.
<boshtannik>
and because, i assume, it can run kivy