[Xastir-dev] Re: [Xastir] Cygwin help

[Daniel H. Brown]

On Mon, 15 Nov 2004, Curt, WE7U wrote:

> Date: Mon, 15 Nov 2004 10:54:59 -0800 (PST)
> From: "Curt, WE7U" <archer at eskimo.com>
> To: Daniel H. Brown <brown at brauhausdc.org>
> Cc: Tom Russo <russo at bogodyn.org>, xastir-dev at xastir.org
> Subject: Re: [Xastir-dev] Re: [Xastir] Cygwin help
> 
> On Sat, 13 Nov 2004, Daniel H. Brown wrote:
>
>> I'd like to suggest this patch:
>>
>>   diff -Naur  xastir-clean/src/map_cache.c   xastir/src/map_cache.c
>> --- xastir-clean/src/map_cache.c        2004-11-13 14:00:19.000000000 +0000
>> +++ xastir/src/map_cache.c      2004-11-13 21:36:09.545714320 +0000
>> @@ -23,10 +23,7 @@
>>    * Look at the README for more information on the program.
>>    */
>>
>> -#ifdef  USE_MAP_CACHE
>> -#warning USE_MAP_CACHE Defined (and there was much rejoicing)
>> -
>> -
>> +#include "config.h"
>>
>>   #include <sys/types.h>
>>   #include <stdio.h>
>> @@ -44,6 +41,12 @@
>>   #include "map_cache.h"
>>
>>
>> +#ifndef  USE_MAP_CACHE
>> +#warning USE_MAP_CACHE NOT Defined
>> +
>> +#else
>> +#warning USE_MAP_CACHE Defined
>> +
>
> Did we mostly duplicate that this morning between Tom's changes and
> mine?

Yes, though, I think "config.h" might aught to be included It wasn't in
the cvs I just downloaded a few minutes ago.

I should have some more updates/patches soon.  Will send them to the -dev
list, when I'm ready, if that is appropriate.  I've been trying to focus on
getting the cache space limits implemented.  I'm probably going to start
using a secondary berkeley db "database" - it shouldn't require a second
file.

As a side note, I'm still struggling with a clock issue under VMware - my
FedoraCore instance running under Windows VMware workstation has a clock
where a second isn't a second long.  It means that - even with clock sync
to OS enabled for vmware and ntpd running in linux, things get out of sync
really quickly.  This causes things like "make" to not always play nice. 
Have spent too much time trying to figure that out, and not enough time
writing c-code.  I believe it is related to the Intel "Speedstep" CPU
clocking adjustments that my laptop does, but, none of the "fixes" I've
been able to find online seem to have any affect.

Anyhow -

More in a bit, after I get some more code writtten.

73 N8YSZ.

--
Dan Brown 
brown at brauhausdc.org