--- Log opened Fri Dec 15 00:00:21 2017
00:38 #navit: < Navit> The following compiles failed: http://download.navit-project.org/logs/navit/android_armv5te/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/osm-exp/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/src/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/openmoko/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/win32/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/n
00:38 #navit: < Navit> oad.navit-project.org/logs/navit/android_armv4t/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/android_x86/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/tomtom/svn/navit-svn-.failed
00:38 #navit: < Navit> See compile results history at http://download.navit-project.org/logs/navit/stats.html
00:40 -!- Horwitz [~mich1@p200300800E014200022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 272 seconds]
00:52 -!- Horwitz [~mich1@p200300800E00D700022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit
00:52 -!- mode/#navit [+o Horwitz] by ChanServ
01:40 -!- j_f-f [~quassel@62.138.18.44] has quit [Ping timeout: 256 seconds]
01:47 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has joined #navit
06:01 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit
06:48 -!- noradtux [~noradtux@2a02:2028:511:901:ec4:7aff:fe33:3dc1] has quit [Ping timeout: 272 seconds]
06:53 -!- noradtux [~noradtux@port-2080.pppoe.wtnet.de] has joined #navit
07:34 -!- naggety [~naggety@2.red-80-27-43.dynamicip.rima-tde.net] has joined #navit
09:06 #navit: < naggety> Hi all
09:06 #navit: < naggety> kazer: are you there?
09:17 -!- AVIC-MRZ02 [d4af773b@gateway/web/freenode/ip.212.175.119.59] has joined #navit
09:33 -!- AVIC-MRZ02 [d4af773b@gateway/web/freenode/ip.212.175.119.59] has quit [Quit: Page closed]
10:06 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Ping timeout: 265 seconds]
11:05 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit
11:12 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Ping timeout: 265 seconds]
11:18 #navit: < jkoan> hi naggety
11:18 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit
11:19 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Client Quit]
11:20 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit
11:30 #navit: < jkoan> Hi naggety
11:45 #navit: < naggety> hi jkoan
11:45 #navit: < jkoan> Probably I could answer the question you had to Kazer?
11:46 #navit: < naggety> Did you see yesterday the problems related to spanish translation in launchpad?
13:28 #navit: < jkoan> No, I don't think I have seen it :/
13:28 #navit: < jkoan> Sorry irc was broken on my side, now it's working again
13:29 #navit: < naggety> In spanish translation file many strings were commented out, so they "disappear"
13:30 #navit: < naggety> We don't know who or what commented that lines out
13:30 #navit: < naggety> But kazer told me to restore a previous .po file and continue translating from it
13:31 #navit: < naggety> I was going to do it, but the .po file we have is a bit outdated, because new strings were added since then
13:31 #navit: < naggety> So I wanted to know how the .po file is updated to get the last added strings to be translated
13:32 #navit: < naggety> Also, I also wanted to comment that I have read that gettext comment the strings that is consider that are obsolete. I think that this is what have happened, but I don't know why
13:49 #navit: < jkoan> Hm okay, I only know that we use launchpad for the translations, but I thought that all use the same base template
14:00 #navit: < youte> hi all
14:01 -!- naggety [~naggety@2.red-80-27-43.dynamicip.rima-tde.net] has quit [Quit: Konversation terminated!]
14:20 #navit: < jkoan> hi youte
14:23 #navit: < youte> i will come back
14:23 #navit: < jkoan> okay :D
14:27 -!- youte [~pi@AStrasbourg-651-1-285-187.w86-235.abo.wanadoo.fr] has quit [Ping timeout: 240 seconds]
14:40 -!- youte [~pi@AStrasbourg-651-1-285-187.w86-235.abo.wanadoo.fr] has joined #navit
15:54 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Quit: Leaving.]
16:47 -!- xenos1984 [~xenos1984@90.191.164.22] has joined #navit
17:22 #navit: < ilovekiruna> hi youte
17:22 #navit: < ilovekiruna> hi jkoan
17:22 #navit: < jkoan> hi ilovekiruna
18:49 #navit: <@KaZeR> hi there
18:49 #navit: < jkoan> Hi KaZeR
18:50 -!- AVIC-MRZ02 [b9e3b653@gateway/web/freenode/ip.185.227.182.83] has joined #navit
18:51 #navit: < jkoan> Hi AVIC-MRZ02
18:52 #navit: < jkoan> KaZeR: could you setup the ci to build for wince today?
18:53 #navit: < AVIC-MRZ02> Hi jkoan
18:54 #navit: < jkoan> AVIC-MRZ02: KaZeR just came online right before you. Probably he could help you today :) or do you have any news?
18:55 #navit: < AVIC-MRZ02> No, I don't have any news.
18:55 #navit: <@KaZeR> jkoan: i might be able to yeah.
18:55 #navit: <@KaZeR> hey AVIC-MRZ02 
18:55 #navit: < AVIC-MRZ02> Hi KaZeR
18:56 #navit: <@KaZeR> i saw the discussion you had with jkoan 
18:56 #navit: <@KaZeR> as jkoan mentioned we were able to fix the wince build. 2 things are left to do : pack in a .cab and finish automating the thing
18:56 #navit: <@KaZeR> both are quite simple, but for the .cab we need to find what's actually needed there
18:57 #navit: < AVIC-MRZ02> I'm not using CAB
18:57 #navit: < jkoan> KaZeR: AVIC-MRZ02 is not using a cab
18:57 #navit: < AVIC-MRZ02> I'm just copying everything to USB and copying to head unit
18:58 #navit: < AVIC-MRZ02> If only the executable will change, all the other files are already on my head-unit
18:58 #navit: <@KaZeR> oh perfect
18:59 #navit: < AVIC-MRZ02> I'll just replace Navi.exe (I changed it's name because head unit tried to execute it automatically)
18:59 #navit: <@KaZeR> how big is your current navit.exe ?
19:00 #navit: < AVIC-MRZ02> Let me check
19:01 #navit: < AVIC-MRZ02> Two days ago, I was using a version with length 4,990,267 bytes
19:01 #navit: <@KaZeR> here's a fresh build : http://sd-55475.dedibox.fr/navit.exe 
19:01 #navit: <@KaZeR> perfect, it's close to what i have here
19:02 #navit: < AVIC-MRZ02> Today I found another version with 5,008,008 bytes
19:04 #navit: <@KaZeR> same ballpark size, so it's probably good
19:05 #navit: < AVIC-MRZ02> I just downloaded the fresh one
19:06 #navit: < AVIC-MRZ02> Now I have to locate to a SUB and go to my car. I'll be back in 10-15 mins.
19:08 #navit: < jkoan> AVIC-MRZ02: wouldn't it be more easy to take the device into the house? ^^
19:20 #navit: < jkoan> KaZeR: do you think we will be able to update the wince toolchain? And should we in fact that wince is very very old?
19:21 #navit: < jkoan> But our goal is always to support old devices. So probably we need to put effort into this?
19:22 #navit: < AVIC-MRZ02> My head-unit's model is around 2014
19:23 #navit: < AVIC-MRZ02> I tried it, I'm hopeless
19:23 #navit: < AVIC-MRZ02> Again the same three lines
19:23 #navit: < AVIC-MRZ02> error:navit:file_init:Maps larger than 2GB are not supported by this binary, sizeof(off_t)=zu
19:23 #navit: < AVIC-MRZ02> error:support_libc:_stat:no file
19:24 #navit: < AVIC-MRZ02> error:navit:main_real:No config file navit.xml, navit.xml.local found
19:24 #navit: < AVIC-MRZ02> May be the problem is related with my OS
19:25 #navit: < AVIC-MRZ02> But there are a lot of cars in my country having more or less the same head-unit
19:25 #navit: < jkoan> I don't know if Kazer added that navit is searching at the binarys directory itself, if not, that's the problem. But this definitely gives us the knowledge that navit itself is running.
19:26 #navit: < AVIC-MRZ02> I said more or less because there are some extra of missing buttons but the OS is exactly the same
19:26 #navit: < jkoan> I don't think the system is the problem :)
19:27 #navit: <@KaZeR> jkoan: i'm not sure that we will be able to update the toolchain. part of the issue is that the toolchain itself hasn't seen a lot of updates in the last 5+ years
19:28 #navit: <@KaZeR> AVIC-MRZ02: that's with the new binary?
19:28 #navit: < AVIC-MRZ02> Sure, from the beginning it's running. I was not aware that an error file is created. After our first chat I've found that file.
19:29 #navit: < AVIC-MRZ02> KaZeR: Yes (I think), let me tell you the file-size
19:30 #navit: < AVIC-MRZ02> 5,135,708 bytes
19:33 #navit: < AVIC-MRZ02> By the way, what's the meaning of first two messages.
19:34 #navit: < AVIC-MRZ02> I downloaded my countrie's map but it is not 2GB, it's only 121.7 MB
19:35 #navit: < jkoan> First means that your file system (probably fat(?)) only support that one file max be 2GB at maximum. It's only generally. So if you want to use Biggers files you need to split them
19:35 #navit: < AVIC-MRZ02> So it's a kind of warning.
19:35 #navit: < jkoan> *may be 2GB
19:36 #navit: < jkoan> Yes
19:36 #navit: < jkoan> Or should be
19:36 #navit: < AVIC-MRZ02> OK I got it, thank you.
19:38 #navit: < jkoan> Hopefully Kazer can do a quick fix for you to test ;)
19:39 #navit: < AVIC-MRZ02> I hope :)
19:40 #navit: <@KaZeR> AVIC-MRZ02: size seems to match. so, there's some good news here. first, our new build process for wince works. so we can easily build tweaked binaries for your device
19:40 #navit: <@KaZeR> AVIC-MRZ02: are you able to specify extra parameters when starting the app ?
19:41 #navit: < jkoan> I can ;)
19:41 #navit: < AVIC-MRZ02> This is one of my problem, I don't have any command line or file manager so I cannot send command line parameters
19:41 #navit: <@KaZeR> AVIC-MRZ02: ok. no big deal i can build something for you hang on
19:42 #navit: <@KaZeR> do you have a "/Storage Card/" path ?
19:42 #navit: < AVIC-MRZ02> Yes, I have path 'USB'
19:43 #navit: < AVIC-MRZ02> Also, I have path 'SD'
19:43 #navit: < AVIC-MRZ02> I think these are the paths that you ask?
19:45 #navit: < jkoan> The Navit binary will get executed by the head which is a blackbox. So my idea would be that we just add that navit searches for the Navit.xml inside the binary path itself. Currently it only searches in the directory from which navit is executed. So if I am in /bla and run ./navit/navit it would search in /bla but we need to add that it also searches inside /bla/navit/
19:45 #navit: <@KaZeR> the code seems to be looking specifically for "/Storage Card" but we can change that
19:45 #navit: <@KaZeR> AVIC-MRZ02: can you try this one ? http://sd-55475.dedibox.fr/navit-a123c97992ecf49f844fa5781d19209a.exe 
19:46 #navit: <@KaZeR> it contains an override for the default debug setting
19:46 #navit: < AVIC-MRZ02> OK
19:46 #navit: < jkoan> Kazer probably wince api has a function for all storage devices, then we Could use that :D
19:48 #navit: < AVIC-MRZ02> I'll be back in a minute
19:58 #navit: < AVIC-MRZ02> I'm back
19:58 #navit: < AVIC-MRZ02> I'm sorry, again the same message
19:58 #navit: < AVIC-MRZ02> This time I also copied the navit.xml file to USB and run the device again
19:59 #navit: < AVIC-MRZ02> may be it's trying to find it from USB, but the result was same
19:59 #navit: < jkoan> This should not be the same result because Kazer enabled debugging
20:00 #navit: < AVIC-MRZ02> By the way, I copied navit.xml to the root of USB (not in any folder)
20:00 #navit: < jkoan> Did you cleaned everything before you tryed and renamed it to navi.exe?
20:01 #navit: < AVIC-MRZ02> Yes, I'm deleting the current navi.exe first, then copying new navi.exe
20:01 #navit: < AVIC-MRZ02> I just write a simple script for that
20:01 #navit: < AVIC-MRZ02> :)
20:02 #navit: < jkoan> Wher do you want to run the script on? On the head itself?
20:03 #navit: < AVIC-MRZ02> There are two files. One of them is 'TESTMODE.KEY' (I Found on internet)
20:03 #navit: < AVIC-MRZ02> the other one is 'scriptexec.ini'
20:03 #navit: < jkoan> What's the content of the second?
20:03 #navit: < AVIC-MRZ02> the second one is a text file that you can write simple command like 'COPY'
20:04 #navit: < AVIC-MRZ02> But unfortunately in scripts there is no command for execution of a file
20:04 #navit: < AVIC-MRZ02> I tried it but it's not working like standard batch files
20:05 #navit: < AVIC-MRZ02> it has it's own commands
20:05 #navit: < jkoan> did you also tryed "start"?
20:05 #navit: < AVIC-MRZ02> for example, in order to delete a file the command is 'REMOVE'
20:06 #navit: < AVIC-MRZ02> I tried 'RUN', 'EXECUTE', 'EXE', 'SHELL'
20:06 #navit: < jkoan> but on windows you use start to run programs ;)
20:06 #navit: < AVIC-MRZ02> but I didn't try 'START'
20:06 #navit: < AVIC-MRZ02> for the executables we're just writing program names
20:08 #navit: < AVIC-MRZ02> Now, I can try if 'START' works
20:08 #navit: < AVIC-MRZ02> if it works, it will be possible to send commands to the application from command line
20:10 #navit: <@KaZeR> AVIC-MRZ02: exactly the same message, no extra lines?
20:11 #navit: < AVIC-MRZ02> Exactly same lines added at the end of old messages
20:15 #navit: < AVIC-MRZ02> I'll check if command 'START' works in a minute.
20:17 #navit: <@KaZeR> that's odd, you should have a "Setting default debug verbosity to 'debug'" message before the "No config file navit.xml, navit.xml.local found"
20:17 #navit: <@KaZeR> ah, my bad hang on
20:18 #navit: <@KaZeR> ok correct binary uploaded
20:18 #navit: <@KaZeR> btw, a123c97992ecf49f844fa5781d19209a (in the name) is the expected md5 checksum for the file
20:20 #navit: < AVIC-MRZ02> Sorry! Now the correct binary is in the same link?
20:21 #navit: <@KaZeR> you're fine, i'm the one who uploaded the wrong binary :)
20:21 #navit: <@KaZeR> yes, same link
20:22 #navit: <@KaZeR> you can double check after downloading using "md5sum navit-a123c97992ecf49f844fa5781d19209a.exe" if you're on Linux
20:22 #navit: < AVIC-MRZ02> OK, I downloaded again
20:22 #navit: < AVIC-MRZ02> I'm completely on Windows :(
20:24 #navit: < ilovekiruna> hi KaZeR
20:24 #navit: <@KaZeR> AVIC-MRZ02: no worries then
20:24 #navit: <@KaZeR> hey ilovekiruna 
20:24 #navit: <@KaZeR> still no news from Fosdem i guess?
20:25 #navit: < ilovekiruna> nope :'(
20:25 #navit: < ilovekiruna> KaZeR: do you have some time to spare for the warnings i didnt understand
20:27 #navit: <@KaZeR> ilovekiruna: yeah i'm back home and should be more available now
20:28 #navit: < ilovekiruna> KaZeR: do you remember the pyton one i asked you i think yesterday?
20:30 #navit: <@KaZeR> yeah i can find it in the logs. it's actually an opportunity to discuss how we want to handle them.
20:30 #navit: < AVIC-MRZ02> KaZeR: Now I have a lots of extra lines
20:30 #navit: < jkoan> AVIC-MRZ02: nice !
20:30 #navit: <@KaZeR> we've probably have dozens of warnings to address, so we might need a way to be efficient at it and avoid work duplication
20:31 #navit: < AVIC-MRZ02> error:navit:main_real:Setting default debug verbosity to 'debug'
20:31 #navit: < jkoan> AVIC-MRZ02: could you upload it to pastebin?
20:31 #navit: < ilovekiruna> right now i still count on my machine around 50
20:31 #navit: <@KaZeR> AVIC-MRZ02: cool! so we will be able to find where navit.xml should go
20:32 #navit: <@KaZeR> you should have a bunch of "Trying <path>" in the logs
20:32 #navit: <@KaZeR> 5 of them if i'm not mistaken
20:33 #navit: < AVIC-MRZ02> May I copy them here quickly, I don't know how to use PasteBin
20:34 #navit: <@KaZeR> you can't really paste 50 lines here on irc. you can just copy and paste in the pastebin form 
20:34 #navit: < AVIC-MRZ02> I Think, I pasted them to PasteBin Now, did you manage to access them?
20:34 #navit: <@KaZeR> cool
20:35 #navit: <@KaZeR> just share the link
20:35 #navit: < jkoan> AVIC-MRZ02:  just go to http://navit.pastebin.com and pase the content there. copy the resulting link and paste it here
20:36 #navit: < AVIC-MRZ02> https://pastebin.com/bdJqX3bX
20:36 #navit: < AVIC-MRZ02> Is it OK? I'm not sure?
20:36 #navit: <@KaZeR> that's perfect
20:36 #navit: <@KaZeR> interesting. it didn't try any of the default paths
20:37 #navit: < AVIC-MRZ02> Good :) Now I can use pastebin.
20:37 #navit: <@KaZeR> oh wait
20:37 #navit: <@KaZeR> "debug:navit:main_real:trying AAA"
20:38 #navit: <@KaZeR> looks like it was intructed to use the config file 'AAA' from the command line
20:38 #navit: < jkoan> yes, thats strange in my eyes
20:38 #navit: <@KaZeR> so it looks like the default call to navi.exe could be "navi.exe -c AAA"
20:38 #navit: <@KaZeR> and that's probably why it's not loading the file from the usual places
20:39 #navit: < jkoan> of AAA is the directory from the head software
20:40 #navit: < AVIC-MRZ02> But it's hidden most probably.
20:40 #navit: < AVIC-MRZ02> There is no AAA directory.
20:42 #navit: <@KaZeR> AVIC-MRZ02: navit-92a36790d578791e692ac07f976969c0.exe should give us the list of parameters passed to the binary
20:44 #navit: < AVIC-MRZ02> You uploaded again?
20:44 #navit: <@KaZeR> yep
20:52 #navit: < AVIC-MRZ02> https://pastebin.com/x23vs48X
20:52 #navit: < AVIC-MRZ02> I think again the same.
20:52 #navit: <@KaZeR> yeah, odd
20:53 #navit: <@KaZeR> might be my fault let me check
20:53 #navit: < jkoan> :D
20:55 #navit: <@KaZeR> let's try navit-fc51032a17c5cc4ed1a8b43574e8268d.exe
20:55 #navit: < AVIC-MRZ02> OK. I'm downloading again
20:56 #navit: <@KaZeR> perfect
20:58 #navit: < AVIC-MRZ02> Opps. Kazer, this time it was my mistake, instead of navit........c.exe, I tried navit.......a.exe
20:59 #navit: <@KaZeR> no worries :)
20:59 #navit: < AVIC-MRZ02> OK now I'll try navit.......d.exe
21:00 #navit: < ilovekiruna> KaZeR: when would you like us to start?
21:01 #navit: <@KaZeR> ilovekiruna: first maybe we should discuss a way to track who's working on which one. there's too many of them to create one ticket per warning though
21:02 #navit: < ilovekiruna> KaZeR: so far i was the only one working on it
21:02 #navit: < ilovekiruna> so no confusion ;-)
21:04 #navit: <@KaZeR> well jkoan did a few, and so did Charles
21:04 #navit: < ilovekiruna> KaZeR: really? What jkoan did, he gave me the patch, i integrated that
21:04 #navit: < ilovekiruna> for Charles jkoan, who asked me to work on it, didnt tell me anything
21:05 #navit: <@KaZeR>  hence the need for a public list, to see what's happening :)
21:06 #navit: < ilovekiruna> i uploaded my warnings.log on pastebin
21:06 #navit: < ilovekiruna> not sure, if it is still active
21:06 #navit: < AVIC-MRZ02> I'm back again with log file
21:06 #navit: < ilovekiruna> but can show u which all are spare
21:06 #navit: < AVIC-MRZ02> https://pastebin.com/Qq8Sx2Cu
21:08 #navit: <@KaZeR> AVIC-MRZ02: sweet. We have the full command line used to start Navi
21:09 #navit: <@KaZeR> let me patch something for you
21:09 #navit: < AVIC-MRZ02> So it's in NAND
21:12 #navit: < AVIC-MRZ02> In some models working navi.exe is in PRG1 and in some models it's in PRG0
21:14 #navit: <@KaZeR> AVIC-MRZ02: navit-35732c26e9a0b595faa62b45fe94d973.exe should drop the AAA arg for your device
21:23 #navit: < AVIC-MRZ02> All directories are listed
21:23 #navit: < AVIC-MRZ02> https://pastebin.com/7URLXGtc
21:24 -!- Celelibi [celelibi@par69-9-88-166-81-29.fbx.proxad.net] has quit [Excess Flood]
21:24 #navit: < jkoan> now you need to fix the xml 
21:24 #navit: <@KaZeR> looks like celebibi should use pastebin :)
21:25 -!- Celelibi [celelibi@88.166.81.29] has joined #navit
21:25 #navit: <@KaZeR> AVIC-MRZ02: can you share the exact file that's at '\NAND\PRG1\APL/navit.xml' ?
21:25 #navit: < jkoan> AVIC-MRZ02: is that the default config?
21:26 #navit: < AVIC-MRZ02> I didn't understand the question?
21:27 #navit: < jkoan> now the content of navit.xml seems to be wrong
21:27 #navit: < AVIC-MRZ02> You're asking the navit.xml file that I'm using?
21:27 #navit: < ilovekiruna> KaZeR: these are my current warnings: https://pastebin.com/Wak5vsFc
21:27 #navit: < jkoan> yep
21:27 #navit: < AVIC-MRZ02> ok.
21:27 #navit: <@KaZeR> AVIC-MRZ02: yes. your file has a typo, or the parser is broken
21:28 #navit: <@KaZeR> ilovekiruna: exactly my point, way too hard to synchronize work like this :)
21:28 #navit: < ilovekiruna> KaZeR: actually first when jkoan asked me to work on it, I was exactly tell that, coordination
21:28 #navit: < ilovekiruna> but info i got was that i am the only one on it
21:29 #navit: < ilovekiruna> KaZeR: also i doubt that we get all the same warnings
21:30 #navit: <@KaZeR> ilovekiruna: well compiling on linux we should get pretty much the same
21:30 #navit: < AVIC-MRZ02> I pasted my navit.xml file https://pastebin.com/EQ2GVW5k
21:31 #navit: < ilovekiruna> KaZeR: i could for example imagine, differences with different gcc versions, or maybe if somebody uses clan instead
21:36 #navit: < jkoan> KaZeR: did you enabled full debugging or only to find the config?
21:36 #navit: <@KaZeR> AVIC-MRZ02: your config file works for me, so the problem is elsewhere
21:36 #navit: <@KaZeR> jkoan: full, i replaced the default debug level
21:37 #navit: < jkoan> okay
21:37 #navit: <@KaZeR> jkoan: i'm thinking that it's not able to open or read the file maybe
21:37 #navit: < AVIC-MRZ02> By the way, I used exactly this config file in the windows version to be sure that it's working
21:37 #navit: < AVIC-MRZ02> there is no problem in windows version also
21:37 #navit: <@KaZeR> ilovekiruna: true, also this would probably be a minority of cases. i expect majority of cases to be actual poor code style :)
21:38 #navit: <@KaZeR> AVIC-MRZ02: ok thanks, it matches what i see
21:50 #navit: <@KaZeR> AVIC-MRZ02: how much memory do you have in your device ?
21:52 #navit: < AVIC-MRZ02> I really don't know. Could the problems be related with the memory amount?
21:53 #navit: <@KaZeR> i'm not sure yet. something isn't right when this block of code is executed on your device : https://github.com/navit-gps/navit/blob/trunk/navit/xmlconfig.c#L1222-L1233
21:53 #navit: <@KaZeR> we do have the output from line 1222
21:54 #navit: <@KaZeR> ohhh
21:58 #navit: <@KaZeR> let's try navit-e11218d286079b299d762a7c8b3e64b6.exe
22:05 #navit: < AVIC-MRZ02> I'm back with logs https://pastebin.com/AvjFizPF
22:16 -!- gegolo [~gegolo@pool-108-26-201-143.bstnma.fios.verizon.net] has joined #navit
22:24 -!- gegolo [~gegolo@pool-108-26-201-143.bstnma.fios.verizon.net] has quit [Quit: Leaving]
22:26 #navit: <@KaZeR> AVIC-MRZ02: ok so we know that ezxml isn't parsing the file correctly now : error:navit:parse_file:Failed to parse file '\NAND\PRG1\APL/navit.xml'
22:27 #navit: <@KaZeR> let's see if we have an alternative
22:27 #navit: < AVIC-MRZ02> OK
22:36 #navit: <@KaZeR> interesting, ezxml should be the parser also used for windows, but you don't have that issue 
22:36 #navit: <@KaZeR> which navit build are you using on windows?
22:37 #navit: < AVIC-MRZ02> just a sec.
22:38 #navit: < AVIC-MRZ02> navit-svn-12258
22:38 #navit: < AVIC-MRZ02> for win32
22:38 #navit: <@KaZeR> -12258? interesting :) where did you get that?
22:39 #navit: <@KaZeR> oh
22:39 #navit: < AVIC-MRZ02> from downloads
22:39 #navit: < AVIC-MRZ02> let me find and give you the address
22:39 #navit: <@KaZeR> wow we need to update that list
22:39 #navit: <@KaZeR> yep got it
22:39 #navit: <@KaZeR> so we are not using svn anymore, since 2 or 3 years
22:41 #navit: < AVIC-MRZ02> http://download.navit-project.org/navit/win32/svn/
22:41 #navit: <@KaZeR> yep thanks. i'll put a note somewhere so that we update that. 
22:41 #navit: < AVIC-MRZ02> It's running on windows 10 :)
22:43 #navit: <@KaZeR> oh yeah, it's just that this one is quite old and missing a few improvements
22:47 #navit: < jkoan> KaZeR: probably move them to "archive"?
22:47 #navit: <@KaZeR> jkoan: i think that we need to replace that listing alltogether with results from the CI instead, and move that to another subdomain yeah
22:49 #navit: < jkoan> That's even better
22:50 #navit: < AVIC-MRZ02> I'm trying to find the memory size but all documentation is in japanese
22:53 #navit: < AVIC-MRZ02> In one of the ad. it says 8GB Flash Memory. This is the only document that I can be found.
22:55 #navit: <@KaZeR> ok. i am trying to see if we can get more details about the parsing failure
22:56 #navit: < AVIC-MRZ02> OK
22:58 #navit: < jkoan> Kazer probably write a little test program to see it parsing generally does not work?
22:59 #navit: <@KaZeR> AVIC-MRZ02: can you please test that binary on your win10? https://4377-30791823-gh.circle-artifacts.com/0/root/project/win32/navit.exe 
22:59 #navit: < AVIC-MRZ02> OK
23:03 #navit: < AVIC-MRZ02> When I try to execute it a black screen comes and suddenly goes
23:05 #navit: <@KaZeR> can you start it from a command line?
23:05 #navit: < AVIC-MRZ02> Interesting.
23:05 #navit: < AVIC-MRZ02> The file that I downloaded was an installation
23:06 #navit: < AVIC-MRZ02> I installed if and it is not working
23:06 #navit: < AVIC-MRZ02> but when I copy only the executable
23:06 #navit: < AVIC-MRZ02> to the directory of old version
23:06 #navit: < AVIC-MRZ02> then it started to work
23:09 #navit: < AVIC-MRZ02> But of course all the images in menu disappeared
23:10 #navit: < AVIC-MRZ02> let me try to execute from command line
23:10 #navit: <@KaZeR> ha, maybe we are missing some files in the installer
23:12 #navit: < AVIC-MRZ02> or may be the config file needs some modification
23:13 #navit: < AVIC-MRZ02> Now I'll try to combine 2 folders
23:15 #navit: <@KaZeR> thanks!
23:16 #navit: < AVIC-MRZ02> OK now it's working. I just combine the old one and new one.
23:18 #navit: <@KaZeR> if you have some time to spare, it'll be useful for us to understand what caused the issue. this could help fix it for the wince build too
23:19 #navit: < AVIC-MRZ02> Spare time right now?
23:19 #navit: <@KaZeR> in general
23:20 #navit: <@KaZeR> investigating this will probably require a few attempts at understanding which file is missing or wrong
23:20 #navit: < AVIC-MRZ02> Of course, we can continue to try.
23:20 #navit: <@KaZeR> but if you can help, it'll save us some time to fix something else, like the fact that win32 binaries were not updated :)
23:20 #navit: <@KaZeR> awesome
23:21 #navit: < AVIC-MRZ02> I can try to help as much as I can, why not.
23:22 #navit: <@KaZeR> that's the spirit!
23:22 #navit: < AVIC-MRZ02> :)
23:22 #navit: <@KaZeR> so, the win32 issue is probably one of the following two :
23:22 #navit: <@KaZeR> - files are missing in the package
23:23 #navit: <@KaZeR> - something is broken in the new package, but wasn't broken in the older package
23:23 #navit: < AVIC-MRZ02> Most probably files are missing because I didn't change new files with olds, I just added some old files
23:25 #navit: <@KaZeR> ok. do you have a list of files?
23:26 #navit: <@KaZeR> could be worth creating a ticket about this issue also : http://trac.navit-project.org/
23:26 #navit: < AVIC-MRZ02> just a sec. I'm trying to do it again :)
23:26 #navit: <@KaZeR> sure thanks :)
23:27 #navit: < jkoan> KaZeR and AVIC-MRZ02 we would like to see devices photos once navit is up and running ;)
23:28 #navit: <@KaZeR> oh yeah absolutely. we'll have to share that on social media too
23:32 #navit: < jkoan> Probably a collage with all devices photos we currently have? :D
23:32 #navit: <@KaZeR> we could do that yeah. but we could also broadcast the fact that we added this new device
23:32 #navit: < AVIC-MRZ02> OK the first problem is the MAP folder
23:32 #navit: < AVIC-MRZ02> There is no MAP folder and map
23:32 #navit: <@KaZeR> this device never worked, as it requires this config tweak for AAA
23:33 #navit: <@KaZeR> AVIC-MRZ02: that's it? easy to fix :)
23:33 #navit: < AVIC-MRZ02> the second one is related with navit.xml file
23:33 #navit: < AVIC-MRZ02> I copied my navit.xml on new one to make it work
23:34 #navit: < AVIC-MRZ02> In one of the pastebins it is available
23:34 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has quit [Ping timeout: 265 seconds]
23:35 #navit: < AVIC-MRZ02> https://pastebin.com/EQ2GVW5k
23:37 #navit: <@KaZeR> so that pasted config works? but not the default one, is that right?
23:37 #navit: < AVIC-MRZ02> yes
23:38 #navit: <@KaZeR> ok thanks
23:42 #navit: < AVIC-MRZ02> KaZeR and jkoan, now I have to sleep (it's about 2 o'clock in the morning), tomorrow I'll try to be here again.
23:42 #navit: <@KaZeR> sure, thanks AVIC-MRZ02 
23:42 #navit: <@KaZeR> i probably won't be here a lot this week-end, but we can talk soon anyway
23:43 #navit: <@KaZeR> thanks for your help troubleshooting. we should be able to make it work soon
23:43 -!- j_f-f [~quassel@62.138.18.44] has joined #navit
23:44 #navit: < AVIC-MRZ02> OK. I'm also waiting to see it's working in head-unit :)
23:44 #navit: < AVIC-MRZ02> see you.
23:45 -!- AVIC-MRZ02 [b9e3b653@gateway/web/freenode/ip.185.227.182.83] has quit [Quit: Page closed]
--- Log closed Sat Dec 16 00:00:23 2017