--- Log opened Mon Oct 15 00:00:20 2018 01:04 #navit: <+Navit> > But what about a bulk update of translations? We only need to verify that the ci passes, but not that the content is correct because this is done on launchpad. Also we can update each translation in one commit to have a similar effect, but with less ci usage 01:04 #navit: <+Navit> True but on the other hand we rarely get updates for several translations at the same time 01:05 #navit: <+Navit> You can see the last updates in launchpad 01:06 #navit: <+Navit> > For map download. Does your curl integration only uses this pre-made api whatever thing or something completely different. And if it does so. Should we use the one provided in map binfile? 01:06 #navit: <+Navit> Nop completely separate 01:06 #navit: <+Navit> I have seen your pm I’ll take care of it when I’ll be back on my laptop 04:21 -!- aerostitch [~aerostitc@c-24-23-228-135.hsd1.ca.comcast.net] has quit [Remote host closed the connection] 04:54 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit 04:54 -!- mode/#navit [+v xenos1984] by ChanServ 09:52 -!- Navit [~Navit@ec2-34-214-224-248.us-west-2.compute.amazonaws.com] has quit [Remote host closed the connection] 11:25 #navit: < genesis> jkoan : does gltt is only for broadcom chip found in a few devices ? 11:25 #navit: <+jkoan> Yes 11:30 #navit: < genesis> PMB2520/hammerhead 14:33 #navit: < Mineque> hi 14:35 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Quit: Leaving.] 15:00 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit 15:01 -!- mode/#navit [+v xenos1984] by ChanServ 15:35 #navit: <+jkoan> Hi Mineque 15:36 #navit: <+jkoan> ilovekiruna: please rework #679 ;) would love to merge it 16:19 #navit: <@KaZeR> hi there 16:27 -!- Navit [~Navit@ec2-34-214-224-248.us-west-2.compute.amazonaws.com] has joined #navit 16:27 -!- mode/#navit [+v Navit] by ChanServ 16:35 #navit: <+jkoan> Hi KaZeR 17:01 -!- Upgreydd [53919cbd@gateway/web/freenode/ip.83.145.156.189] has joined #navit 17:01 #navit: < Upgreydd> Good afternoon everyone. I have a question, does navit support static linking for cross compilation for some nonstandard platforms? 17:31 #navit: < genesis> jkoan : do you know a good tomtom obd software and do u have some bt dongle ? 17:31 #navit: < genesis> should get my tomtom one XL in 25 minutes :D 17:38 #navit: <@KaZeR> Upgreydd: hi! 17:39 #navit: <@KaZeR> Upgreydd: this might break the plugins usage. Do you have more details? 17:43 #navit: <@KaZeR> genesis: obd as in obd-ii? 17:46 -!- Upgreydd_ [53919cbd@gateway/web/freenode/ip.83.145.156.189] has joined #navit 17:47 #navit: < Upgreydd_> KaZeR: I'm trying to compile via qnx 6.5.0 crosscompiler but failing a lot :/ 17:47 -!- Upgreydd [53919cbd@gateway/web/freenode/ip.83.145.156.189] has quit [Ping timeout: 256 seconds] 17:47 #navit: <@KaZeR> Upgreydd_: are you the person that contacted me last week via LinkedIn? 17:47 #navit: < Upgreydd_> KaZeR: No known features for CXX compiler "GNU" version 4.4.2. 17:47 #navit: < Upgreydd_> KaZeR: I think that was Phillou? :D 17:48 #navit: < Upgreydd_> KaZeR: I have a lot of LinkedIn users too, Don't know your name there 17:49 #navit: <@KaZeR> it was someone named Greg. No worries i was just wondering 17:49 #navit: < Upgreydd_> OK, so there's an option to compile for QNX? 17:49 #navit: < Upgreydd_> :D 17:51 #navit: <@KaZeR> we can probably make it work. Can you share more logs (via pastebin) and more details about your build env? 17:51 #navit: < Upgreydd_> Kazer, sure. I have whole QNX 6.5.0 stack installed with crosscompiler, one second 17:54 #navit: < Upgreydd_> KaZeR: https://pastebin.com/iRHWVarc 17:55 #navit: < Upgreydd_> CMAKE toolchain + CMakeError.log 17:56 #navit: < Upgreydd_> qcc is QNX gcc with additional things: http://www.qnx.com/developers/docs/6.5.0/index.jsp?topic=%2Fcom.qnx.doc.neutrino_utilities%2Fq%2Fqcc.html 17:57 #navit: < Upgreydd_> KaZeR: theres a normal GCC too, but the same error as above 17:58 #navit: <@KaZeR> and you don't have files like endian.h in your cross compiler env? 17:58 #navit: <@KaZeR> (i'm not familiar with qnx) 17:59 #navit: < Upgreydd_> KaZeR: /opt/qnx650/target/qnx6/usr/include/io-pkt/machine/endian.h 17:59 #navit: < Upgreydd_> I have something like this 18:01 #navit: < Upgreydd_> LD_LIBRARY_PATH=/opt/qnx650/host/linux/x86/usr/lib 18:04 #navit: < genesis> KaZeR : yes , cost a few bucks and help to diagnostic engine, i've repaird my car in the old day with such elm327 dongle 18:04 #navit: < genesis> i get the tomtom :) 18:05 #navit: <@KaZeR> genesis: yep definitely useful. i have 2 myself. i'm not aware of an app for tomtom though. The only open app i know of is openobd which is written in python 18:05 #navit: <@KaZeR> genesis: sweet! 18:05 #navit: <@KaZeR> Upgreydd_: have you been able to build other apps using your toolchain? 18:05 #navit: < genesis> yes i think that was the one i hacked in the day 18:06 #navit: < genesis> with jupyter 18:07 #navit: < Upgreydd_> KaZeR: I wasn't compiling anything 18:10 #navit: <@KaZeR> Upgreydd_: so your qnx cross compilation env is new? you've never used it before? 18:24 #navit: < Upgreydd_> KaZeR: yep, now tried with this https://raw.githubusercontent.com/open62541/open62541/master/tools/cmake/Toolchain-QNX-6.5.0.cmake 18:25 #navit: < Upgreydd_> ` Failed to find "GL/gl.h" in "/usr/include/libdrm".` 18:29 #navit: <@KaZeR> Upgreydd_: have to go afk 1h - can help you after that 18:29 #navit: < Upgreydd_> KaZeR: thank you, I'll wait 18:30 #navit: <+ilovekiruna> jkoan: would love to rework it 18:31 #navit: <+ilovekiruna> I just have no clue at all how to 18:31 #navit: <@KaZeR> Upgreydd_: in the meantime if you can tell me more about your target platform it could help (board, etc) 18:31 #navit: < Upgreydd_> KaZeR: here or at PM? 18:33 #navit: <@KaZeR> here is fine for me, that way someone else might be able to help 18:39 #navit: < Upgreydd_> I know only few usecases of QNX system, it's used in BlackBerry phones and car entertainment. It's very simmilar to BSD, have own kernel loading system called IFS. It's packed uboot with all boot required files, but it can use script files. QNX can be baset on multiple CPU architectures, starting from arm, x86, x86_64 and other multiprocessors from OMAP family and others. As I said before it's simmilar to linux/bsd systems, so it h 18:39 #navit: <+jkoan> genesis: for both, I don't know. I need very head one and therefore I also don't know a software 18:39 #navit: < Upgreydd_> structure, like /etc /bin /usr 19:04 -!- ilovekiruna [~ilovekiru@ip1f12af77.dynamic.kabel-deutschland.de] has quit [Remote host closed the connection] 19:37 -!- ilovekiruna [~ilovekiru@ip1f12af77.dynamic.kabel-deutschland.de] has joined #navit 19:37 -!- mode/#navit [+v ilovekiruna] by ChanServ 19:37 #navit: <@KaZeR> Upgreydd_: how did you setup your cross compilation env? 19:38 #navit: <+ilovekiruna> KaZeR: any more ideas on FOSDEM or Sailfish container? 19:39 #navit: <@KaZeR> regarding fosdem, one thing we did since last year was to setup a buildroot env. i wonder how interesting that is 19:41 #navit: <+ilovekiruna> I guess the presentation was now taken as a first batch submission not 19:41 #navit: <+ilovekiruna> sure 19:41 #navit: <+ilovekiruna> would rather think to now come up with another presentation 19:41 #navit: <+ilovekiruna> just in case 19:50 #navit: <@KaZeR> regarding buildroot i'm wondering how much of it makes sense for a fosdem talk. Took us some work to integrate it, but our use case is quite generic 19:51 #navit: < genesis> i dont think buildroot so relevant for OS with desktop/ui 19:52 #navit: <@KaZeR> i would beg to disagree. It's quite awesome to build a ready to use image. 19:52 #navit: <@KaZeR> want to test navit on a raspberry pi? just flash our image, and you're ready to go 19:52 #navit: < genesis> choice, i prefer openembedded 19:53 #navit: < genesis> i work a lot on that, i did the first distribution of aldebaran's nao on that 19:53 #navit: <@KaZeR> oh nice 19:53 #navit: < genesis> and i think last tomtom use it too, like hertz rental service in a previous job 19:53 #navit: <@KaZeR> they don't list a lot of boards there though 19:54 #navit: < Upgreydd_> KaZeR: I'm back 19:54 #navit: < genesis> but also i like openembedded since it's higher level of packaging, like gentoo / bsd OS, recipe based, not makefile 19:54 #navit: <@KaZeR> genesis: looks like we need a navit package for openembedded :) 19:56 #navit: < genesis> and with openembedded, is easier to share software between plateform 19:56 #navit: < genesis> ipkg package 19:59 -!- Upgreydd_ [53919cbd@gateway/web/freenode/ip.83.145.156.189] has quit [Quit: Page closed] 20:12 #navit: <+Navit> Gen 20:13 #navit: <+Navit> Ups :D 20:13 #navit: <+Navit> Genesis, do you think that we can add support for tomtom to open embedded? 20:15 #navit: < genesis> yes, main difficulty is to begin to 20:15 #navit: < genesis> first you have to write a device config, that's easy 20:15 #navit: < genesis> then you have to write a distribution, that's quite easy 20:16 #navit: < genesis> but where we lost time is to make software version reliable 20:17 #navit: < genesis> http://cgit.openembedded.org/openembedded/tree/conf/machine/navman-icn330.conf example of a device conf 20:21 #navit: < genesis> i don't work on that stuff since years, need to understand the scheme of the differente repository 20:32 #navit: <+Navit> Okay, I think I will look into it once I have time. But sounds interesting. Probably this could help to speed up the dev process of NavitTom 21:54 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.] --- Log closed Tue Oct 16 00:00:22 2018