[Xastir] A few changes

[Tom Russo]

On Sat, May 04, 2019 at 07:09:28PM -0500, we recorded a bogon-computron collision of the <kg4wsv at gmail.com> flavor, containing:
> I didn???t read Curt???s email closely enough (a number LIKE .... indicating git version) so I did it twice on my pi, once with the update script and once with a new clean clone. Both worked. I was confused at first until I realized it was compiling fine, I just wasn???t seeing warnings. :|
> 
> When making librtree.a there???s a message from ar 
> 
> ar: ???u??? modifier ignored since ???D??? is the default (see ???U???)

Well know issue with GNU automake and libtool.  Been a problem for ages
and they haven't fixed it yet.

Google "automake ar modifier ignored" and you'll see tons of packages 
complaining about it.

> But About tells me I have rtree support and librtree.a exists so its apparently informational. 

Just ignore it.  Sometime in the next 10 years they'll get it fixed.

> > On Apr 30, 2019, at 9:58 AM, Curt Mills <curt.we7u at gmail.com> wrote:
> > 
> > 1) After updating from Git you'll see a new message in the configure
> > summary:
> > 
> >    RECOMMENDED OPTIONS:
> >      Xpm / Snapshots ........................... : yes
> > 
> > If you have libxpm and libxpm-dev packages installed (the names of the
> > packages may vary on your system) then you'll see a "yes" there. That
> > enables the Snapshot facility in Xastir. That was somewhat hidden before,
> > perhaps only greying-out the button in the menus if it wasn't present
> > during configure/compile.
> > 
> > 2) In the Help->About dialog you'll see at the very top something like:
> > 
> >    Xastir V2.1.1 (cf75dd5a)
> > 
> > That last number is the 8-digit short-form version of the most recent Git
> > commit. That tells you _exactly_ which code is in your compile.
> > 
> > 3) You may notice an absence or a severe reduction in compile warnings.
> > This is a result of multiple people working over the last 1.5 weeks on this
> > particular issue (Issue #24). We still have a few warnings related to
> > geotiff / graphicsmagick / imagemagick: These appear to be problems in
> > their headers, not our code. With a very new GCC compiler (7 or 8?) you may
> > also see a bunch of messages about snprintf but there exist some compiler
> > flags which will quiet those: We're using them in one of our Travis-CI
> > configs to do just that.
> > 
> > 4) While working on #3 above we found some real bugs and worked to fix them
> > or in some cases add them to our bug list.
> > 
> > 5) Travis-CI is building Xastir every time there is a commit or a pull
> > request. It currently builds on three Ubuntu-16.04 systems and one OSX
> > 10.13.3 system and feeds back warnings/errors to us. You can see this at:
> > https://travis-ci.org/Xastir/Xastir
> > Thanks to Jason Godfrey for setting this up. We're worked quite a bit on
> > the configuration in the last week to make it do what we want.
> > 
> > 6) The project is currently at zero pull requests and only a few
> > outstanding bugs.
> > https://github.com/Xastir/Xastir
> > 
> > -- 
> > Curt, WE7U        http://we7u.wetnet.net        http://www.sarguydigital.com
> > _______________________________________________
> > Xastir mailing list
> > Xastir at lists.xastir.org
> > http://xastir.org/mailman/listinfo/xastir
> _______________________________________________
> Xastir mailing list
> Xastir at lists.xastir.org
> http://xastir.org/mailman/listinfo/xastir

-- 
Tom Russo    KM5VY
Tijeras, NM  

 echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m]