[01:20:54] *** Quits: Horwitz (~mich1@p200300ec9f01cd00022268fffe64e7c4.dip0.t-ipconnect.de) (Ping timeout: 246 seconds) [01:33:47] *** Joins: Horwitz (~mich1@p200300ec9f274f00022268fffe64e7c4.dip0.t-ipconnect.de) [01:33:47] *** ChanServ sets mode: +o Horwitz [06:44:41] *** Quits: owler (~owlman@61-68-86-34.tpgi.com.au) (Quit: Konversation terminated!) [06:46:52] *** Joins: owlman (~owlman@61-68-86-34.tpgi.com.au) [07:42:44] *** Quits: owlman (~owlman@61-68-86-34.tpgi.com.au) (Quit: Konversation terminated!) [07:43:31] *** Joins: owlman (~owlman@61-68-86-34.tpgi.com.au) [08:35:42] mvglasow: an alternative solution to the problem with image conversion within gradle wold be to skip it and use the svg's directly which would also have the benefit of reduced apk size and faster build time, but the downside that we need to render them on the device which could have problems because its not powerfull enought [08:37:34] also we need to look at xml's and the transations. Those 3 things are currently handled by cmake. And this is also the reason why we head the cmake in the build_android.sh in the first place. Hope to get this sorted out [10:57:11] jkoan I had a suspicion that this is what the first cmake is for: generate makefiles for images, xml and translations [10:57:32] which, I understand, needs to happen before gradle assembles the APK [10:58:19] but the kludge we're currently using comes at the cost of building a full set of binaries and then throwing it away [10:58:52] possible approaches (though I don't know how feasible they are) would be: [10:59:26] run a stripped-down cmake before gradle, just enough to generate the makefiles for the things we need to run through make [11:00:11] or invoke make from gradle, after cmake runs (or alternatively a drop-in replacement for make) [11:15:53] or is there a way to invoke make for these three things from cmake? [11:17:31] just browsing the Android developer docs, externalNativeBuild also suports a ndkBuild element, which takes an Android.mk file, which is a GNU makefile fragment... [11:17:58] though I don't know what happens if externalNativeuild has both cmake and ndkBuild children: is this allowed at all, and do they run in a particular order? no idea... [12:38:57] btw, some progress on the source tree pollution issue: https://github.com/navit-gps/navit/pull/1094 keeps the CMake generated stuff in a separate subdir [12:39:37] there are still some leftovers in navit/android, but these are three dirs which can be deleted [12:43:19] *** Quits: ilovekiruna (~ilovekiru@2a02:8108:d00:110:c148:52f5:d957:d25) (Ping timeout: 272 seconds) [13:10:55] *** Joins: ilovekiruna (~ilovekiru@ip1f12afe2.dynamic.kabel-deutschland.de) [13:10:55] *** ChanServ sets mode: +v ilovekiruna [13:42:16] *** Quits: mvglasow (~mvglasow@78-61-158-97.static.zebra.lt) (Ping timeout: 240 seconds) [13:55:16] *** Joins: mvglasow (~mvglasow@78-61-158-97.static.zebra.lt) [14:33:11] I just pushed another commit to #1094, now all Android build artifacts are contained in one build dir [21:48:08] @mvglasow, great, thanks for your work :-)