I've played with it some and and have not found any issues. I put together a BPQ packet node in January, and I haven't fully back-filled what I had "stolen" from aprs, so testing capability is fairly limited. From what I can tell, though, it's nice and stable.
I do have a few questions about the source ( yeah, always one in the crowd :-) ) - In dlm.c noticed references to "curl-multi" and evidently the capability to leverage parallel downloading of map tiles as supported by libcurl. Is whether or not that is supported in our platform based on what version of curl is installed? - now that dlm.c handles downloading tiles, is there anything left in tile_mgmnt.c that is still needed or could tile_mgmnt.h and tile_mgmnt.c be removed? It seems at a minimum the "getOneTile" portion of tile_mgmnt.c is no longer needed. Looks like you guys are doing a lot of cleanup in this release, so brought that up just in case there's some stuff there that could be streamlined a bit. Fyi, my Odroid XU4 (arm based) beats the pants off my Intel Celeron based laptop in terms of map download speed. Both are on Ubuntu 18.04 with the MATE desktop. Am wondering if the fact that the XU4 has an octa-core cpu makes a difference with respect to curl-multi. The cleaner compiling is very noticeable, and the earlier note about newer compilers spitting out more warnings matches what I saw. Compiling is cleaner in Debian Stretch and Ubuntu 16.04 than it is in Ubuntu 18.04, but it still builds fine. (And even in Ubuntu 18.04 the new code still compiles a lot cleaner that the older code did) Thanks, Lee K5DAT On Thu, May 9, 2019 at 9:57 AM Curt Mills <[email protected]> wrote: > We're planning to do a release within a few weeks. It might be as few as 2 > weeks. > > Please check out / compile / thrash on the latest Github Xastir code. Find > anything that broke with our latest code fixes. Exercise all types of > interfaces, messaging, bulletins, weather stations, tracking, following > stations, maps, etc. Anything you can think of. > > The latest code compiles much cleaner and a lot of fixes went in to make > that possible. We'd like this release to function well, so whatever you can > do to exercise the code would be most appreciated. > > If you find a bug or odd operation, report it here: > > https://github.com/Xastir/Xastir/issues > > Thanks! > > -- > Curt, WE7U http://we7u.wetnet.net > http://www.sarguydigital.com > _______________________________________________ > Xastir mailing list > [email protected] > http://xastir.org/mailman/listinfo/xastir > _______________________________________________ Xastir mailing list [email protected] http://xastir.org/mailman/listinfo/xastir
