On Sat, 15 Nov 2008, Lee Bengston wrote: > On 11/15/08, Tom Russo <[EMAIL PROTECTED]> wrote: >> On Fri, Nov 14, 2008 at 11:42:40PM -0600, we recorded a bogon-computron >> collision of the <[EMAIL PROTECTED]> flavor, containing: >> > ------snip----- > >> > Fyi, I also installed the geotiff packages from the ubuntu repository >> > instead of using the get-maptools script. Knowing from recent >> > experience with other Debian based distros that the header files get >> > installed in /usr/include/geotiff, I copied them into /usr/include >> > before compiling Xastir, and it seems happy with that. >> >> >> This is probably not best practice, as those copies will not be updated if >> the package is updated. >> >> Better practice would be to tell configure to add /usr/include/geotiff to >> the search path, which is easily done: >> /path/to/configure CPPFLAGS="-I/usr/include/geotiff" >> >> Then you don't have orphaned copies of geotiff headers, and configure can >> still find the ones that the package installs in the nonstandard place. >> > > For my own use, it's probably 6 one way and half a dozen the other. > If I do the configure mod, I'll lose it every time I rebuild Xastir. > For a pre-built VM to be distributed to others, I think I'll just > install geotiff from souce as shown in the wiki.
How'z about creating symlinks in /usr/include to the real spot instead? That way it picks up any updates and Xastir's configure can still find the package. Another alternative might be to tweak the xastir update script in your distributed VMWare image to include the configure option and insist that people use that to upgrade to the latest CVS. -- Curt, WE7U. archer at eskimo dot com http://www.eskimo.com/~archer Lotto: A tax on people who are bad at math. - unknown Windows: Microsoft's tax on computer illiterates. - WE7U. The world DOES revolve around me: I picked the coordinate system!" _______________________________________________ Xastir mailing list [email protected] http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
