[Xastir] Xastir stable release 1.9.6

[Chip G.]

On v10.6.1:

> xastir 1.9.6 has been configured to use the following
> options and external libraries:
>
> MINIMUM OPTIONS:
>   ShapeLib (Vector maps) ................. : yes
>
> RECOMMENDED OPTIONS:
> -n   GraphicsMagick/ImageMagick (Raster maps) :
> yes (GraphicsMagick)
>   pcre (Shapefile customization) ......... : yes
>   dbfawk (Shapefile customization) ....... : yes
>   rtree indexing (Shapefile speedups) .... : yes
>   map caching (Raster map speedups) ...... : yes
>   internet map retrieval ................. : yes (libcurl)
>
> FOR THE ADVENTUROUS:
>   AX25 (Linux Kernel I/O Drivers) ........ : no
>   libproj (USGS Topos & Aerial Photos) ... : yes
>   GeoTiff (USGS Topos & Aerial Photos) ... : yes
>   Festival (Text-to-speech) .............. : no
>   GDAL/OGR (Obtuse map formats) .......... : no
>   GPSMan/gpsmanshp (GPS downloads) ....... : no
>
> xastir will be installed in /sw/bin.
> Type 'make' to build Xastir (Use 'gmake' instead on some systems).

Got these warnings, but installed fine...

> --------------------        Compiling the Files         
> --------------------
>
> Making all in src
> Making all in rtree
> draw_symbols.c: In function ‘draw_deadreckoning_features’:
> draw_symbols.c:3542: warning: cast from pointer to integer of  
> different size
> main.c: In function ‘Configure_defaults’:
> main.c:22884: warning: comparison with string literal results in  
> unspecified behaviour
> main.c:22886: warning: comparison with string literal results in  
> unspecified behaviour
> main.c:22888: warning: comparison with string literal results in  
> unspecified behaviour
> map_geo.c: In function ‘draw_geo_image_map’:
> map_geo.c:1880: warning: implicit declaration of function  
> ‘DestroyImagePixels’
> objects.c: In function ‘Set_CAD_object_parameters_dialog’:
> objects.c:2541: warning: ‘clsd_menu’ may be used uninitialized in  
> this function
> x_spider.c:811: warning: ‘old_progname’ defined but not used
> x_spider.c:811: warning: ‘old_progname_full’ defined but not used
> ld: warning: duplicate dylib /sw/lib/libproj.0.dylib
> ld: warning: duplicate dylib /sw/lib/libtiff.3.dylib
> ld: warning: duplicate dylib /sw/lib/libjpeg.62.dylib
> ld: warning: duplicate dylib /usr/lib/libz.1.dylib
> ld: warning: duplicate dylib /sw/lib/libproj.0.dylib
> ld: warning: duplicate dylib /sw/lib/libtiff.3.dylib
> ld: warning: duplicate dylib /sw/lib/libjpeg.62.dylib
> ld: warning: duplicate dylib /usr/lib/libz.1.dylib
> ld: warning: duplicate dylib /sw/lib/libproj.0.dylib
> ld: warning: duplicate dylib /sw/lib/libtiff.3.dylib
> ld: warning: duplicate dylib /sw/lib/libjpeg.62.dylib
> ld: warning: duplicate dylib /usr/lib/libz.1.dylib
> Making all in m4
> Making all in config
> Making all in help
> Making all in scripts
> Making all in symbols
> Making all in callpass
> ld: warning: duplicate dylib /sw/lib/libproj.0.dylib
> ld: warning: duplicate dylib /sw/lib/libtiff.3.dylib
> ld: warning: duplicate dylib /sw/lib/libjpeg.62.dylib
> ld: warning: duplicate dylib /usr/lib/libz.1.dylib

Runs like a champ ... Will install on my Tiger system later ...  
(working 12 hr nights, 4 on, 1 off until Nov)

On Oct 10, 2009, at 23:51, Keith Kaiser wrote:

> I am curious if any other Mac users out there have had this problem,  
> and if so did they find a solution. But resolving this issue is not  
> worth getting everyone all worked up about it. I understand getting  
> things working on all platforms is not an easy thing, I can wait  
> until someone else solves it. I'm not strong enough in Linux (yet)  
> to do it myself.



--
     Chip