On Sat, Nov 15, 2008 at 2:09 PM, Tom Russo <[EMAIL PROTECTED]> wrote:
> On Sat, Nov 15, 2008 at 11:46:56AM -0600, we recorded a bogon-computron 
> collision of the <[EMAIL PROTECTED]> flavor, containing:
>> 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.
>
> Not entirely true.  The configure options are stored in config.log and
> config.status, and if you simply do a "make" when configure has changed,
> configure will be rerun with the same options you used last time.  Or you
> can cut/paste from the comment line of config.log that captures the
> line that you used last time.

Thanks - did not realize the options were stored in separate files.

> Or you can do what I do: keep a file in your build directory called
> "reconfigure" and then run ". ./reconfigure" instead of remembering the
> options you needed to get it done.

I like that.

>> For a pre-built VM to be distributed to others, I think I'll just
>> install geotiff from souce as shown in the wiki.
>
> It's very annoying that the packagers of the Ubuntu (and Debian?) geotiff
> package chose to place the header files in a nonstandard location.

Yes, I've seen exactly the same thing in Mepis and DreamLinux, which
are Debian based.   There's a gdal binary available as well (for the
newer versions of Ubuntu, Mepis, and DreamLinux), which I have not
tried yet.

Lee - K5DAT
_______________________________________________
Xastir mailing list
Xastir@xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir

Reply via email to