<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Install a development environment (specifically, you'll need git to get started)</div><div class=""><br class=""></div><div class="">mkdir ~/src</div><div class="">cd ~/src</div><div class="">git clone <a href="git://github.com/Subsurface-divelog/subsurface" class="">git://github.com/Subsurface-divelog/subsurface</a></div><div class="">less subsurface/INSTALL</div><div class="">in there you'll find a list of packages to install, including the command to do it</div><div class="">after that has completed</div><div class="">./subsurface/scripts/build -both</div><div class="">should do the trick.</div><div class="">I have no personal experience with Mint 17.3 MATE - so it's entirely possible that this is one of the distros that make things harder than they have to be, but the steps above should get you a local build environment for desktop and mobile version</div><div class="">Building an Android .apk is a bit more painful, but subsurface/<span style="background-color: rgb(255, 255, 255);" class="">packaging/android/README should point you in the right direction.</span></div><div class=""><br class=""></div><div class="">Answering questions like this for every person who wants to engage with Subsurface doesn't scale. I'm copying the list so hopefully the next person will find this in the archives. But also so that if you have follow up questions you please copy the mailing list so that others might chime in.</div><div class=""><br class=""></div><div class="">/D</div><br class=""><div><blockquote type="cite" class=""><div class="">On Sep 12, 2018, at 5:25 PM, Bill Perry <<a href="mailto:bill@billandterrie.com" class="">bill@billandterrie.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Dirk,<br class="">I'm back to looking at the Pelagic download issue for the Atmos AI.<br class="">Things should go faster this time as I'm familiar with things in Subsurface<br class="">and I think I have a handle on what the current issues are.<br class=""><br class="">I've lost my old development & build environment and I'll need to create a new Subsurface build environment to test things.<br class="">You had given me some general directions in the past.<br class="">As I recall it was a bit complicated to get things set up just right to do the builds.<br class="">Could I get a few quick pointers or information as to where to the git sources, the needed build tree structure<br class="">and how fire off the build for the mobile app?<br class="">I'm currently using Linux Mint 17.3 MATE 64 bit.<br class="">I'm assuming I can build subsurface mobile on this platform.<br class=""><br class=""><br class="">In terms of what I've seen. There appears to be timing delay problems in a few places in libdivecomputer.<br class="">The libdivecoputer code is trying to do certain timing delays but it appears that they are simply not working at all on Android. like nanosleep() is not working.<br class="">I can put in some more robust code to ensure that the delays always work properly even if the calls to functions like nanosleep() are interrupted and return immediately.<br class="">I think once this is fixed that the downloads on Android - at least for the Pelagic Data cable and for the Atmos AI should start working on the Galaxy S7.<br class="">This delay issue is likely affecting all dive computers using FTDI cables as typically there are some critical timing delays that must be done during initialization and if the<br class="">delays are too short the host will never be able to communicate with the PIC inside the data cable or dive computer.<br class="">One thing that perhaps I may update as well is that there are 3 types of initializations that have to be done to be able to communicate with<br class="">the dive computer and currently if any of them failed (at least with the early Pelagic devices) libdivecomputer logs a message that says it couldn't open up the serial device.<br class="">This can be misleading.<br class="">For example currently I'm seeing that the port open is working just fine and it is able to send data across the serial port and the first message to initialized the data cable is failing<br class="">but yet the log says the port open failed.<br class=""><br class="">--- bill<br class=""><br class=""><br class=""></div></div></blockquote></div><br class=""></body></html>