--- Log opened Sun May 14 00:00:11 2017
00:13 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit
00:21 #navit: < kazer> ilovekiruna: you are close, but there's two things :
00:22 #navit: < kazer> 1) speed_exceed_limit_offset is an attribute defined in attr.h, not a property of the osd.
00:22 #navit: < kazer> it is used like this : https://github.com/navit-gps/navit/blob/trunk/navit/osd/core/osd_core.c#L2663
00:23 #navit: < kazer> and set like this https://github.com/navit-gps/navit/blob/trunk/navit/osd/core/osd_core.c#L2795-L2799 when the osd is created
00:23 #navit: < kazer> technically we could update the attribute using something like command='speed_exceed_limit_offset == 0 ? 10 : 0'
00:24 #navit: < kazer> this does update the attribute. But the issue 2) is that when the osd is redrawn, the attribute isn't refresh. It is set only once, in osd_speed_warner_new()
00:26 #navit: < kazer> unfortunately currently is is not easy to refresh attributes when an osd is redrawn, as this would require access to the 'struct attr **attrs' that are used at the osd creation time
00:26 #navit: < kazer> so we need to find another way :)
00:27 #navit: < kazer> btw : instead of a compass, you can use a button osd for this. <osd type="button" src="icon.svg" command="..." />
00:28 #navit: < kazer> you can also check the value of the offset in realtime by adding this before line 2663 :
00:28 #navit: < kazer> dbg(lvl_debug, "speed_exceed_limit_offset : %f\n", this->speed_exceed_limit_offset);
00:28 #navit: < kazer> and then enable debugging for that function by adding this somewhere at the beginning of your navit.xml :
00:29 #navit: < kazer> <debug name="osd_core:osd_speed_warner_draw" dbg_level="debug"/
01:54 #navit: < kazer> ilovekiruna: https://github.com/navit-gps/navit/commit/5ca60166243b0671b4a7e62938b13feacd2391e2 should do what you asked for. This commit makes the speed warner enabled state toggable on click
01:54 #navit: < kazer> no command required in the osd definition
02:27 -!- circleci-bot [~circleci-@54.144.64.239] has joined #navit
02:27 #navit: < circleci-bot> Success: pgrandin's build (#1887; push) in navit-gps/navit (master) -- https://circleci.com/gh/navit-gps/navit/1887?utm_campaign=chatroom-integration&amp;utm_medium=referral&amp;utm_source=irc
02:27 -!- circleci-bot [~circleci-@54.144.64.239] has quit [Client Quit]
05:13 #navit: < ilovekiruna> kazer: setting the speed limit to zero disables the speed warner? I just intended a strict limit
05:17 #navit: < ilovekiruna> so would an alternative to define two speed_warners with a different limit offset and then switch them by a button or sth else? I used the compass to avoid another button and keep my osd simplistic as possible
07:38 -!- ilovekiruna [~ilovekiru@b2b-130-180-113-170.unitymedia.biz] has quit [Ping timeout: 260 seconds]
09:41 -!- noradtux [~noradtux@port-33545.pppoe.wtnet.de] has quit [Ping timeout: 240 seconds]
09:41 -!- noradtux [~noradtux@port-54615.pppoe.wtnet.de] has joined #navit
11:35 -!- pini [~pini@bou-fi.pustule.org] has joined #navit
11:42 -!- ilovekiruna [~ilovekiru@b2b-130-180-113-170.unitymedia.biz] has joined #navit
12:57 #navit: < kazer> ilovekiruna: good catch. i did not understood your needs correctly
12:58 #navit: < ilovekiruna> kazer: any new ideas?
12:58 #navit: < kazer> one possible approch would be to have two attributes for the offset, and switch between them when clicking (instead of disabling the warner)
12:58 #navit: < kazer> this should not be difficult
12:59 #navit: < ilovekiruna> what do u mean by "attributes"?
12:59 #navit: < ilovekiruna> two different speed_warners?
12:59 #navit: < kazer> no, more like a property of the speed warner osd
12:59 #navit: < kazer> we usually call them attribute because of the way they are read from the xml and stored internally in navit
13:00 #navit: < ilovekiruna> right now I am not sure how i can do this.
13:01 #navit: < kazer> something like <osd type="speed_warner" speed_exceed_limit_offset="15" speed_exceed_limit_offset_strict="0" />
13:02 #navit: < kazer> this one should be quite easy. i can guide you if you want
13:02 #navit: < ilovekiruna> would be nice
13:02 #navit: < ilovekiruna> I want two different limits, when traveling abroad
13:02 #navit: < ilovekiruna> some countries are more strict ;-)
13:03 #navit: < ilovekiruna> and then the switch happens in the command?
13:05 #navit: < kazer> we could make the switch happen when clicking on the osd item for now, that's the easiest
13:06 #navit: < kazer> ideally for more flexibility we can have make the attribute updateable, but it's a bit more involved (not a lot, but a bit)
13:06 #navit: < kazer> how's your C knowledge?
13:07 #navit: < ilovekiruna> working, I would asy
13:07 #navit: < ilovekiruna> say
13:07 #navit: < kazer> perfect :)
13:07 #navit: < ilovekiruna> not perfect though ;-)
13:07 #navit: < kazer> so first, create a git branch for this (we'll submit it as a PR later)
13:07 #navit: < ilovekiruna> on github?
13:08 #navit: < kazer> did you use git clone to fetch the code? or did you download a zip archive?
13:08 #navit: < ilovekiruna> so far I didnt download code yet, but am on github
13:08 #navit: < ilovekiruna> so can just branch it and clone locally
13:08 #navit: < kazer> ok. so first step would be to fork (because you don't have access to our repo yet)
13:09 #navit: < kazer> then clone your fork
13:09 #navit: < kazer> then create a branch
13:09 #navit: < ilovekiruna> navit-gps/navit, right?
13:09 #navit: < kazer> that's the one
13:10 #navit: < ilovekiruna> forked and cloned
13:10 #navit: < kazer> great. git checkout -b "a_fancy_name_for_your_branch"
13:10 #navit: < ilovekiruna> oki
13:11 #navit: < ilovekiruna> where to continue?
13:14 #navit: < kazer> first, let's create the attribute that we need to load the config from the xml. attributes are declared in attr_def.h
13:15 #navit: < kazer> look for the block that contains the one we want to duplicate ( speed_exceed_limit_offset ) and add your need attribute at the end of that block (it's important to add it at the end to not break things)
13:16 #navit: < kazer> so between those two :
13:16 #navit: < kazer> ATTR(nav_status)
13:16 #navit: < kazer> ATTR2(0x00027500,type_rel_abs_begin)
13:16 #navit: < kazer> actually maybe position matters only for maps.. this would make sense
13:17 #navit: < kazer> yeah, so scratch that and let's add it in the speed_warner block instead. The order restriction should only be for map items
13:18 #navit: < ilovekiruna> am confused now
13:18 #navit: < kazer> :)
13:18 #navit: < ilovekiruna> add sth in attr_def or not?
13:18 #navit: < kazer> yep
13:18 #navit: < kazer> https://github.com/navit-gps/navit/blob/trunk/navit/attr_def.h#L164
13:18 #navit: < kazer> that's how we are going to read the value from the xml
13:19 #navit: < ilovekiruna> ok
13:19 #navit: < ilovekiruna> added it
13:19 #navit: < ilovekiruna> at the position u told me
13:19 #navit: < kazer> so we need to add it, but we can add it on line 165 where it makes sense instead of the end of the ATTR block
13:19 #navit: < ilovekiruna> lovely
13:19 #navit: < ilovekiruna> done
13:19 #navit: < kazer> good. what did you call it?
13:20 #navit: < ilovekiruna> speed_exceedd_limit_strict
13:20 #navit: < ilovekiruna> so one could hv a tighter and a weaker bound
13:20 #navit: < kazer> perfect. now add that attribute to the xml definition of your osd in navit.xml and we are going to read it
13:22 #navit: < ilovekiruna> ok, done
13:22 #navit: < kazer> ok. now for the actual reading
13:23 #navit: < kazer> in osd/core/osd_core.c we need to add a property in our osd's struct
13:23 #navit: < kazer> https://github.com/navit-gps/navit/blob/trunk/navit/osd/core/osd_core.c#L2592
13:23 #navit: < kazer> to store the value
13:24 #navit: < ilovekiruna> ok
13:24 #navit: < kazer> then we need to load the value when we init the osd : https://github.com/navit-gps/navit/blob/trunk/navit/osd/core/osd_core.c#L2818-L2822
13:24 #navit: < kazer> and then we are almost done
13:26 #navit: < kazer> (i would default to this->speed_exceed_limit_offset if we can't find the value, so that the strict value is the same as the normal value when undefined
13:26 #navit: < ilovekiruna> good idea
13:29 #navit: < ilovekiruna> hope, it is done
13:29 #navit: < kazer> you can add a dbg(lvl_debug ...) statement to check if it works, and then enable debugging for that function using <debug name="osd_core:osd_speed_warner_new" dbg_level="debug"/> in your xml
13:29 #navit: < kazer> next we need a place to store if we should care about the normal or the stricter value
13:31 #navit: < kazer> we could add an int strict_mode; declaration inside the osd's struct. Make it default to 0 when we initialize the osd, and change the code in osd_speed_warner_click() to toggle the strict attribute instead of the active one
13:32 #navit: < ilovekiruna> that can be then refreshed when clicking?
13:32 #navit: < kazer> what can be refreshed ?
13:32 #navit: < kazer> we want to toggle it when we click
13:32 #navit: < ilovekiruna> yes,
13:32 #navit: < kazer> :)
13:32 #navit: < kazer> just change this line : https://github.com/navit-gps/navit/blob/trunk/navit/osd/core/osd_core.c#L2730
13:34 #navit: < ilovekiruna> the strict_mode was again in attr_def and then in osd_core?
13:35 #navit: < kazer> we don't need it in attr_def, becaue we are not going to load it from the xml. it only needs to be part of the speed warner's osd  struct
13:35 #navit: < kazer> like a private property
13:35 #navit: < ilovekiruna> so just in osd_core?
13:35 #navit: < kazer> yep
13:37 -!- robertp [5849c97e@gateway/web/freenode/ip.88.73.201.126] has joined #navit
13:37 #navit: < kazer> hey robertp
13:37 #navit: < robertp> Hi, that was fast, kazer.
13:37 #navit: < robertp> :D
13:37 #navit: < kazer> was waiting for you ;)
13:37 #navit: < kazer> did you see the QML2 poc PR ?
13:37 #navit: < ilovekiruna> ok, added the int property in the struct
13:37 #navit: < kazer> perfect. one last thing to do : https://github.com/navit-gps/navit/blob/trunk/navit/osd/core/osd_core.c#L2664 is where the magic happens
13:37 #navit: < robertp> Yes, of course,and I will test and try tonight.
13:38 #navit: < robertp> I have a question to this PR
13:38 #navit: < kazer> robertp: great! this is going to be awesome for the multimedia playback because the components will be able to self refresh
13:38 #navit: < kazer> ilovekiruna: do you get the logic at the line i shared? we just need to change that to (if strick, use the strict value, otherwise use the default one)
13:38 #navit: < robertp> Is there a receipe to set up the qt dependencies? I tried metalstrolchs build on RPi and it failed anyhow (i dont remember anymore)
13:39 #navit: < kazer> ah. yeah qt can be a pain to setup. on my dev machine i've used ./qt-unified-linux-x64-2.0.5-2-online.run wizard. haven't tried on the pi yet
13:40 #navit: < ilovekiruna> kazer: I am right now trying to understand the logic
13:41 #navit: < kazer> ok, let me know if you have questions
13:41 -!- jfitie [4df99fa5@gateway/web/freenode/ip.77.249.159.165] has joined #navit
13:41 #navit: < robertp> brb: rock the kid to bed
13:41 #navit: < kazer> robertp: you never rock me to bed :(
13:41 #navit: < kazer> hey jfitie
13:41 #navit: < jfitie> Hi
13:42 #navit: < kazer> i've seen your PR for the icon improvements. It's a bit difficult to review as-is and i'm trying to think of a better way to do it. I haven't fogotten you :)
13:44 #navit: < ilovekiruna> kazer: am wondering now, if I couldnt solve my needs even simpler
13:44 #navit: < jfitie> Excellent :-). Sleske also did some work on icons; f.ex. https://github.com/navit-gps/navit/commit/21e49b3ec396e0cd54b11c5e56f19d7fb1c838cd. Would be good to do this all the same way. Maybe some short page in the wiki about icon styles (describing outlines etc.)?
13:44 #navit: < ilovekiruna> what if I just would set the percent level to zero and change from && to ||
13:45 #navit: < kazer> ilovekiruna: this would solve your own need, but might break it for other users
13:45 #navit: < ilovekiruna> yeah, true :(
13:46 #navit: < kazer> jfitie: excellent idea. having a consistent style is really important
13:47 #navit: < kazer> btw : we could even have a theme using OSM's icons : https://github.com/openstreetmap/map-icons
13:47 #navit: < kazer> (which did not exist when we created our current theme)
13:48 -!- robertp [5849c97e@gateway/web/freenode/ip.88.73.201.126] has quit [Ping timeout: 260 seconds]
13:48 #navit: < kazer> looks like robertp rocked it too hard :_
13:50 #navit: < kazer> ilovekiruna: if you need a pointer, i think that this should do it : https://gist.github.com/pgrandin/b49b6a2fa8f24da8de6936e77b040c65
13:51 #navit: < kazer> triple check these parenthesis ;)
13:53 #navit: < ilovekiruna> kazer: was almost there myself, but u r faster ;-)
13:53 #navit: < kazer> cool :)
13:53 #navit: < kazer> then it's test time \o/
13:55 -!- robertp [5849c97e@gateway/web/freenode/ip.88.73.201.126] has joined #navit
13:55 #navit: < kazer> jfitie: on what platform are you using navit ?
13:56 #navit: < ilovekiruna> kazer: ok, would then try to compile it.
13:56 #navit: < kazer> jfitie: since you seem to have an interest for the design part, you might be interested in this : https://github.com/navit-gps/navit/pull/254
13:57 #navit: < kazer> ilovekiruna: yep
13:58 #navit: < ilovekiruna> kazer: will take a while, also need to install more required packages. Usually I run navit on Android
13:59 #navit: < kazer> ok. just let us know if you need help
13:59 #navit: < kazer> btw : since you now have a fork of navit, you can benefit from our automated builds
14:00 #navit: < kazer> using circleci
14:00 #navit: < kazer> if you push your code to youre repo, we can trigger builds using circleci, and you would end up with an apk in 15-20 min
14:01 #navit: < robertp> Kazer, looking at ci, the test system changed a lot - is there a(n easy) way to clone the ci settings of navit-gps's account?
14:01 #navit: < kazer> robertp: you just need the circle.yml file
14:01 #navit: < robertp> We should probably document that o.O
14:02 #navit: < kazer> some stuffs won't work (like pushing to launchpad or signing the apk) but they should be restricted to our repo
14:02 #navit: < robertp> No. My tests will fail for some reason and I dropped the ci tests for my fork becaus of that
14:02 #navit: < robertp> e
14:02 #navit: < kazer> robertp: we should indeed :) now is a good opportunity
14:02 #navit: < kazer> robertp: want to look into it now?
14:03 #navit: < kazer> here's an example of filtering on our repo : https://github.com/navit-gps/navit/blob/trunk/ci/build_linux.sh#L5 for coverity scans
14:03 #navit: < ilovekiruna> kazer: not that u get surprised, my github id isnt ilovekiruna
14:03 #navit: < kazer> no worries. mine isn't kazer :)
14:04 #navit: < kazer> robertp's isn't robertp :)
14:04 #navit: < robertp> and mine isn't robertp :D
14:04 #navit: < robertp> argh. too slow
14:04 #navit: < kazer> hehe
14:04 #navit: < kazer> yeah maybe i had too much coffee already :D
14:05 #navit: < robertp> kazer, i forgot how to add my fork to ci o.O
14:05 #navit: < kazer> robertp: if you log in the circleci app, authenticate using github, you should see your repos
14:05 #navit: < kazer> you can follow / unfollow projects from there
14:05 #navit: < robertp> HAHA FOUND IT!!!!
14:06 #navit: < kazer> :)
14:06 -!- pmckinley [~peter@88-110-203-198.dynamic.dsl.as9105.com] has joined #navit
14:06 #navit: < kazer> hey pmckinley
14:07 #navit: < pmckinley> hey
14:07 #navit: < pmckinley> gonna pm u
14:07 #navit: < kazer> you might be interested in this. With ilovekiruna we're adding a new feature to the speed warner osd, to enable a default speed limit offset, and the possibility to switch to a stricter offset
14:09 -!- Netsplit *.net <-> *.split quits: @Horwitz
14:09 #navit: < ilovekiruna> kazer: ok, pushed my branch to github
14:11 #navit: < pmckinley> Hi kazer
14:11 #navit: < pmckinley> hi ilovekiruna
14:11 #navit: < ilovekiruna> hi pmckinley
14:11 #navit: < robertp>  Kazer, you wrote "I'll put some notes in the wiki about this." can I find some info how to set up the qml gui to be able to test and try?
14:12 #navit: < pmckinley> im confused, you can already configure 2 offsets, % and miles per hour over
14:12 #navit: < pmckinley> and set them both to zero
14:12 #navit: < ilovekiruna> hi pmckinley
14:12 #navit: < pmckinley> hi
14:12 #navit: < ilovekiruna> I want often travel between countries
14:12 #navit: < kazer> robertp: note the future tense :D
14:12 #navit: < ilovekiruna> some countries are more picky on speed limits, so I would like to easily switch
14:12 #navit: < pmckinley> I think the default is 10 and 15 already
14:13 #navit: < pmckinley> I set both to zero
14:13 #navit: < pmckinley> I have NO tolerance :)
14:13 #navit: < kazer> pmckinley: the idea is more like "driving through germany : 15, passing the french border : switching to 0" :)
14:13 #navit: < pmckinley> which is how it should be hehe
14:13 #navit: < robertp> I have it set to 19, and it's often complaing. :D
14:13 #navit: < pmckinley> tut, naughty
14:13 #navit: < ilovekiruna> robertp: That was what I also thought
14:13 #navit: < pmckinley> what country are you from robertp, so I can avoid it ;)
14:13 #navit: < ilovekiruna> sometimes it can be rally annoying
14:14 #navit: < pmckinley> know what would be REALLY  while you're at it looking at speed_warner
14:14 #navit: < pmckinley> cool*
14:14 #navit: < kazer> ilovekiruna: keep in mind that everything is configurable in navit (or can be made so) including warner's timeouts
14:15 #navit: < pmckinley> for the alert to repeat until the overspeed is corrected ;)
14:15 #navit: < ilovekiruna> kazer: I had that adventure years ago, on a nice Palm Pre
14:15 #navit: < pmckinley> because
14:15 #navit: < ilovekiruna> not anymore
14:15 #navit: < ilovekiruna> :(
14:16 #navit: < pmckinley> if you miss the message because Stevie Nicks was playing too loud, like reaching the crescendo of Rooms On Fire, the damage is done
14:16 -!- Netsplit over, joins: Horwitz
14:16 -!- mode/#navit [+o Horwitz] by ChanServ
14:16 #navit: < pmckinley> hi Michael ;)
14:16 #navit: < robertp> Kazer: https://circleci.com/gh/pohlinkzei/navit/229
14:16 #navit: < ilovekiruna> kazer: Is the build running?
14:16 #navit: < kazer> pmckinley: haha
14:17 #navit: < robertp> pmckinley: for that reason navit should silent the music.
14:17 #navit: < kazer> ilovekiruna: were you using navit on a palm pre?
14:17 #navit: < pmckinley> :/
14:17 #navit: < ilovekiruna> kazer: back in those days, yes
14:17 #navit: < kazer> robertp: +1, long live audio_framework !
14:17 #navit: < robertp> Kazer: yes, it was running.
14:17 #navit: < kazer> ilovekiruna: sweet! so you're not a new user!
14:18 #navit: < robertp> audio framework isnt born yet ;(
14:18 #navit: < ilovekiruna> kazer: now on Android, but would love if one of u guys manages a qt5 port to use it on sailfish
14:18 #navit: < pmckinley> silence the music? never! Philistine :)
14:18 #navit: < robertp> ok, jyst decrease the volume
14:18 #navit: < robertp> jyst?
14:18 #navit: < robertp> just
14:18 #navit: < robertp> !
14:19 #navit: < pmckinley> not an option
14:19 #navit: < pmckinley> :-D
14:20 #navit: < kazer> ilovekiruna: https://github.com/navit-gps/navit/pull/239 qt5 is done and working.
14:20 #navit: < kazer> ilovekiruna: work on a qt5/qml ui has started : https://github.com/navit-gps/navit/pull/254/ you're welcome to contribute :)
14:20 #navit: < kazer> pmckinley: what about just reducing the volume for a few seconds? :)
14:21 #navit: < kazer> robertp: your build fails because of ci/build_tomtom_minimal.sh: line 96: tomtom.cache: Permission denied
14:21 #navit: < pmckinley> I keep my hands on the wheel at all times :)
14:21 #navit: < ilovekiruna> kazer: right now I try to get some chat protocols to work on sailfish
14:21 #navit: < kazer> pmckinley: that's the trick : we can now do it in software, automatically
14:21 #navit: < ilovekiruna> kazer: if i find time, which is unfortunately not so likely, would be nice to contribute
14:21 #navit: < ilovekiruna> start phd the next month
14:21 #navit: < kazer> ilovekiruna: nice congrats
14:22 #navit: < pmckinley> kazer: pmckinley: that's the trick : we can now do it in software, automatically
14:22 #navit: < pmckinley> explain!
14:22 #navit: < kazer> btw contribution could be ideas, reviews, test, doesn't have to be code :)
14:22 #navit: < pmckinley> :)
14:22 #navit: < ilovekiruna> three years of painful work ;-)
14:22 #navit: < kazer> pmckinley: with the audio_framework it becomes possible to lower the volume of a softvol mixer. So the music volumes gets lowered, announcment is made, volume goes back to normal
14:22 #navit: < kazer> ilovekiruna: haha yeah
14:23 #navit: < pmckinley> how are you interfacing with the in-car entertainment system? Mine is about 20 years old!
14:23 #navit: < robertp> Kazer, https://circleci.com/gh/navit-gps/navit/1795 suceeded on navit-gps account, so there must be a difference
14:24 #navit: < pmckinley> but it's an interesting gimic ;)
14:25 #navit: < pmckinley> I think to repeat would be more effective, I can set the announcement to be whatever I want it to be :)
14:25 #navit: < robertp> pmckinley: https://hackaday.io/project/8128-navit-on-a-vw-oem-navigation-system one option to interface car audio and navit
14:27 #navit: < pmckinley> I used to use the aux input, connected to my Raspberry Pi, but I missed John Hannah on Mellow Magic, the Darth Vader of pop radio
14:27 #navit: < pmckinley> so i upgraded to a speaker
14:28 #navit: < kazer> pmckinley: trash that! build your own :)
14:28 #navit: < pmckinley> Let me check that link......does it want my credit card details and bank account number?
14:28 #navit: < pmckinley> :-D
14:28 #navit: < pmckinley> >:o
14:29 #navit: < pmckinley> kazer: build my own computer???
14:29 #navit: < kazer> pmckinley: what about listening to them on spotify or using mpd ? we have code for that :)
14:29 #navit: < kazer> pmckinley: https://hackaday.io/project/3070-the-cherokee-carputer
14:30 #navit: < pmckinley> Hey I think I know that guy.....
14:30 #navit: < pmckinley> :)
14:30 #navit: < kazer> :D
14:31 #navit: < robertp> kazer: can you give me a hint to set up the qml gui?
14:38 #navit: < kazer> robertp: sure. do you have qt5 installed?
14:38 #navit: < robertp> Jawohl! It built successfully and cmake recognised all qt5 potions
14:41 #navit: < ilovekiruna> robertp: Would that run on sailfish?
14:41 -!- pini [~pini@bou-fi.pustule.org] has quit [Ping timeout: 268 seconds]
14:41 #navit: < robertp> ilovekiruna: what should run on Sailfish?
14:42 #navit: < ilovekiruna> the qt5 port
14:42 #navit: < kazer> robertp: great. then it should be piece of cake. enable the qt5 graphics :  <graphics type="qt5"/> and the qt5_qml gui :  <gui type="qt5_qml" enabled="yes"/> and it should work
14:42 #navit: < robertp> I am using lunix only
14:42 #navit: < kazer> ilovekiruna: yes it should
14:43 #navit: < ilovekiruna> hmm, then maybe one should try to give it a shot on the mer-obs
14:43 #navit: < kazer> ilovekiruna: the qt5 driver has been developped and tested against sailfish
14:43 #navit: < ilovekiruna> if I find some time in the coming days, would try
14:44 #navit: < robertp> kazer: WOOHOO, it works
14:44 #navit: < kazer> ilovekiruna: metalstrolch 's fork is focusing on sailfish and he regularly submit PRs against our repo : https://github.com/metalstrolch/navit (he also contributes directly to our repo)
14:44 #navit: < kazer> robertp: that was easy :)
14:45 #navit: < robertp> kazer: what should actually work?
14:45 #navit: < kazer> robertp: want to kickstart the wiki doc? :) i'd be interested in the steps you followed to install qt5 on the pi, haven't done it yet
14:45 #navit: < ilovekiruna> kazer: Has metalstrolch already a packaged version for openrepos?
14:46 #navit: < kazer> robertp: it's really a poc for now. you can list maps, and list pois around you. that's it :) but with your help we can do much more! :D
14:46 #navit: < ilovekiruna> or rather on?
14:46 #navit: < robertp> OK, I'll try to get it working on my PI
14:46 #navit: < robertp> On my VM it works
14:49 -!- jfitie [4df99fa5@gateway/web/freenode/ip.77.249.159.165] has quit [Quit: Page closed]
14:50 #navit: < kazer> ilovekiruna: i believe so, but i'm unsure. we still need to streamline this
14:59 #navit: < ilovekiruna> kazer: tried to compile now on my gentoo machine
15:00 #navit: < ilovekiruna> didnt work, will check if there are topos
15:00 #navit: < kazer> gentoo FTW! \o/
15:00 #navit: < ilovekiruna> typos*
15:00 #navit: < ilovekiruna> gentoo hardened!
15:00 #navit: < kazer> nice :)
15:04 #navit: < ilovekiruna> yes, had typos :(
15:04 #navit: < ilovekiruna> was afraid of that
15:04 #navit: < ilovekiruna> will push corrected version, soon
15:04 #navit: < kazer> i'm looking into robert's CI issue, then we can get the CI to build automatically for you too
15:05 #navit: < ilovekiruna> kazer: no problem, just tell me, when u r on it
15:09 #navit: < robertp> kazer, I am missing a ssh key at my ci setup? Is this needed?
15:10 #navit: < robertp> navit-gps does have one
15:12 #navit: < kazer> robertp: the ssh key is used to do the merge from trunk to master from the ci. You should not need one
15:13 #navit: < robertp> mh... so what do the environment vaiables do?
15:13 #navit: < kazer> which one ?
15:13 #navit: < robertp> the one I need to geht things working :D
15:18 #navit: < robertp> I see those: COVERITY_EMAIL COVERITY_PROJECT COVERITY_TOKEN HUB_TOKEN HUB_USER KEY SP key_name lp_cookie
15:18 #navit: < robertp> The other settings are the same, i think
15:19 #navit: < kazer> Coverity* is for the coverity code analysis. hub is to merge trunk into master, sp and keyname are for apk signing. lp_cookie is for launchpad trasnlations update
15:19 #navit: < kazer> so you should not need any of these
15:25 #navit: < robertp> so it should work, I guess
15:32 #navit: < kazer> robertp: are you building against precise or trusty?
15:32 #navit: < robertp> trustty
15:32 #navit: < kazer> ok
15:32 #navit: < kazer> 100% sure?
15:33 #navit: < robertp> yup
15:34 #navit: < kazer> oki
15:48 #navit: < kazer> robertp: i reproduced your issue on a fresh clone in a fresh repo : What was agreed to, and when
15:48 #navit: < kazer> crap wrong paste
15:48 #navit: < kazer> https://circleci.com/gh/pgrandin/navit/290
15:52 #navit: < kazer> ah, i know what's happening :)
15:53 #navit: < kazer> it does not fail on our main CI because we use multiple parallel containers.
15:53 #navit: < kazer> https://github.com/navit-gps/navit/blob/trunk/ci/build_tomtom_plugin.sh#L227
15:54 #navit: < kazer> when we build tomtom plugin then minimal (or the other way around) it changes the permissions on the cache folder
16:07 #navit: < robertp> so its the circle.yml?
16:11 #navit: < kazer> it's the build scripts for tomtom in circleci yeah. I'm fixing them
16:12 #navit: < kazer> yeah our current build for tomtom is overkill. we build it twice, when we should just need to pack a few more files for the plugin one
16:15 #navit: < robertp> I am looking forward to this, thanks kazer
16:26 #navit: < kazer> np. meanwhile in your fork you can just disable the tomtom builds, but it should be fixed soon
16:27 #navit: < robertp> sorry for dumb questions: how?
16:47 #navit: < kazer> it's not dumb :) the easiest way is to change this line : https://github.com/navit-gps/navit/blob/trunk/circle.yml#L31 to only pick the scripts you want to run. for you, i'm guessing build_linux.sh
16:47 #navit: < kazer> it will speed up the tests in your own CI
16:51 #navit: < kazer> ilovekiruna: the same trick would allow you to build for android right now
16:53 #navit: < ilovekiruna> kazer: sorry, which trick?
16:54 #navit: < kazer> https://github.com/navit-gps/navit/blob/trunk/circle.yml#L31 if you change "ci_build_*.sh" to "ci_build_android.sh" it will only build an apk for android
16:54 #navit: < kazer> (in your own circleci fork)
16:54 #navit: < ilovekiruna> ah, I c
16:55 #navit: < ilovekiruna> kazer: should the bahs also run successful on my linux machine?
16:56 #navit: < ilovekiruna> or are there any strong circleci specific adjustments?
16:56 #navit: < kazer> they should, assuming that you have ndk properly setup. You would probably have to tweak some paths
16:56 #navit: < robertp> No, kazer. To test the build on linux is easy. I develop on linux and I am the first who gets errors on build. With ci I prevent my commit to break other builds.
16:57 #navit: < kazer> our ci is really just a trusty container with a few extra packages
16:57 #navit: < kazer> robertp: ah! then give me a few more time, and you should be able to test for all platforms :)
16:57 #navit: < robertp> no hurry :)
16:58 -!- robertp [5849c97e@gateway/web/freenode/ip.88.73.201.126] has quit [Quit: bye]
17:32 #navit: < ilovekiruna> kazer: hv built it now on cirlceci
17:33 #navit: < ilovekiruna> when driving next will test it
17:33 #navit: < ilovekiruna> probably on tuesday
17:42 -!- Celelibi [celelibi@46.187.203.77.rev.sfr.net] has quit [Ping timeout: 268 seconds]
17:42 -!- Celelibi_ [celelibi@46.187.203.77.rev.sfr.net] has joined #navit
18:00 #navit: < kazer> ilovekiruna: cool
18:00 #navit: < kazer> ilovekiruna: you can also test it using the Demo vehicle
18:00 #navit: < ilovekiruna> kazer: how?
18:08 #navit: < kazer> you can enable the Demo vehicle in navit.xml
18:08 #navit: < kazer> then if you set a position and a destination, it will follow the route
18:09 #navit: < kazer> default speed is 40 km/h i believe
19:38 #navit: < pmckinley> Hi Roomies
19:40 -!- Horwitz [~mich1@p200300800E27B500022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 272 seconds]
19:45 #navit: < pmckinley> hi kazer
19:45 -!- pmckinley [~peter@88-110-203-198.dynamic.dsl.as9105.com] has quit [Remote host closed the connection]
19:52 -!- Horwitz [~mich1@p200300800E00AF00022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit
19:53 -!- mode/#navit [+o Horwitz] by ChanServ
19:59 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.]
--- Log closed Mon May 15 00:00:12 2017