From XastirWiki
Jump to: navigation, search

Installing on FreeBSD

Xastir runs very well on FreeBSD. There are 2 easy ways to install Xastir on FreeBSD.

Use the package

pkg_add -r xastir

This requires an ftp connection to the internet and will download Xastir, and the default prerequisites as binary packages and install them. This will install a default config which includes;

  • Shapelib
  • Perl Compatible Regular Expressions
  • DBFAWK
  • Image Magick

Use the port

FreeBSD has an excellent ports system which downloads and builds software from source. It automatically resolves dependancies and provides a menu interface allowing you to configure various options before compilation.

With the port, the following options are also available;

  • ImageMagick or GraphicsMagick selection
  • GeoTIFF - Tiff based georeferences raster imagery
  • GDAL - Extra GIS file formats
  • GPSMAN - GPS interface
  • Festival - speech synthesis
  • RTREE - Spatial indexing of shapefiles
  • Tiger Map Caching using Berkeley DB

Install the port

  1. Install the FreeBSD Ports Tree
  2. cd /usr/ports/comms/xastir
  3. make config
  4. make install

or, use the portinstall port.

See the entry below about a port for tracking the bleeding edge.

Track the "bleeding edge"

While the FreeBSD ports system will get you the latest stable release quickly and easily, it can also help you track the unstable Git version, too.

To do this, install xastir with all the options you want according to the instructions under "Install the port" above. Since the ports system will download and install all the packages xastir depends on, and will do so by installing full development packages with headers and libraries, this will get you the full development environment you need to build the Git version of xastir, too.

After doing that, deinstall the xastir port:

 # pkg_delete xastir'*' 

This is necessary before you install the Git version, because if you leave it installed then the Git version will overwrite files that the package database keeps track of, and the system will be confused.

Make sure you have the two "gnu-autotools" ports for automake and autoconf installed:

 # pkg_info | grep gnu-auto 

This command should show you two lines. If not, install them:

 # cd /usr/ports/devel/gnu-automake
 # make install clean

This will install both gnu-automake and gnu-autoconf.

Before continuing (no longer as root), make sure your PATH variable is set so that the automake and autoconf versions you just installed are found first:

 $ export PATH=/usr/local/gnu-autotools/bin:$PATH

Now you are ready to build xastir from its CVS repository, per the directions in README.GIT, which can be found at:

https://github.com/Xastir/Xastir/blob/master/README.GIT

or on this wiki at Notes:Git.

Use the following configure command when you get to that step in README.CVS:

 ./configure  --with-rtree --with-bdb-incdir=/usr/local/include/db42 CPPFLAGS="-I/usr/local/include" LDFLAGS="-L/usr/local/lib" CFLAGS="-O"

(you can omit the two --with- options if you are not building with RTREE or map caching.) This will make sure that the configure program can find all the headers and libraries that FreeBSD has in /usr/local, which is different from linux where nearly everything gets installed to /usr instead.

A port to keep you current!

NOTE: The text in this section references an old port that will no longer work now that the project has moved to git. The port described below is still set up to pull Xastir from sourceforge. We have left the section intact because you may find it useful to construct your own port that references git instead by using this port as a starting point.]

This is a FreeBSD port skeleton designed to let you keep up with the current Xastir Git tree.

Unfortunately the FreeBSD ports tree really isn't setup for this sort of port so it won't be appearing there. Instead please download it from

http://www.stagecraft.cx/software/xastir-devel.tar.gz

There is one issue with this port. As of its creation date it correctly lists all included files in the pkg-plist and so an uninstall will cleanly remove them. This is almost certainly going to change and installs in the future will probably leave files around. At least until the port skeleton is updated.

It should, however, remove the majority of the files and it's most likely that new files will appear in one of the xastir specific directories making it easy to find them later.

Installing

Download the port skeleton and extract it into a working directory. It will create a directory called "xastir-devel" and place the skeleton within.

Using it is *exactly* like installing a normal port except you can't use portinstall, portmaster or similar. Follow the steps below;

 cd xastir-devel
 make config (select what options you would like to build with)
 make
 make install
 make clean

It will install all dependancies as required. It will, by default use the version of Sleepycat DB (BDB) that is installed as long as it is at least version 4.1. If you want to use a later version of BDB then just install it first. The port will pick the latest installed version to use. If you don't have BDB installed, it will install version 4.1 by default.

This port installs into the same locations as the standard comms/xastir port so you can't have both installed at the same time. It will complain if you try.

Keeping Current

The port extracts the source via CVS each time you run it so updating to the current CVS HEAD is as simple as doing

 make
 make deinstall
 make reinstall

Since it downloads from CVS each time you can't easily go back to a previous version using this port. If you want to keep a port binary around you can do a "make package" after you have done the "make install" to create a binary package that you can re-install as you wish.

Problems

If you have problems with the port contact me at the address below. I do read both the xastir and xastir-dev mailing lists.

Enjoy!


Carl,
(vk1kcm)
carl at stagecraft dot cx