[Flightgear-devel] Problems solved!

2002-01-22 Thread Erik Hofman



AAARGH!

After five days of searching for what the hell was going on I discovered 
mk4.h contains:

#define bool int

One lousy line ruining your life! Yuck.

If you get all sorts of strange error messages, you have to remove that 
line.

Erik
:(


___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel



Re: [Flightgear-devel] Problems solved!

2002-01-22 Thread Erik Hofman

Erik Hofman wrote:


> After five days of searching for what the hell was going on I discovered 
> mk4.h contains:
> 
> #define bool int
> 
> One lousy line ruining your life! Yuck.
> 
> If you get all sorts of strange error messages, you have to remove that 
> line.


Could we abandon MetaKit completely please?
The 2.4.2-32 version which is supplied by SimGear doesn't compiler 
properly. I vote for using David's plain text sulution (at least for now).

Erik



___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel



Re: [Flightgear-devel] Problems solved!

2002-01-22 Thread Alex Perry

> Could we abandon MetaKit completely please?
> The 2.4.2-32 version which is supplied by SimGear doesn't compiler 
> properly. I vote for using David's plain text sulution (at least for now).

I don't recall David's solution.

It seems to me that we're only using MK for doing simple record lookups in 
basic tables (no joins) with a match on one string or a number range.
With that being the case, why can't we use a simple text format store ?

As far as doing quick searches, I'd rather have the indexes compiled into
the table as character offsets that define a balanced binary tree.
It's easy to generate, and to ignore when doing non-indexed searches.
The default file is only 50k records, requiring 16 record fetches for
an arbitrary search.  I would expect those blocks to reside in cache.
People with lots of memory are welcome to use 4MB to store the data.

Of course, a side effect would be that someone would have to rewrite
a lot of code in the src/Airports directory to use the other library.
Since that wouldn't be me, I don't see that as a significant problem 8-).

___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel



Re: [Flightgear-devel] Problems solved!

2002-01-22 Thread Erik Hofman

Norman Vine wrote:

> Erik Hofman writes:
> 
>>
>>Could we abandon MetaKit completely please?
>>The 2.4.2-32 version which is supplied by SimGear doesn't compiler 
>>properly. I vote for using David's plain text sulution (at 
>>least for now).
>>
> 
> I really don't care what we do any more but  .
> 
> I am assuming this is Irix

Yep.



> Did you try
> 
>  % cd SimGear/simgear/metakit
>  % cd builds
>  % ../unix/configure
>  % make



That part is still working, but I don't see the reason for using that 
one after we have decided to unbundle it. I expect a package to work 
after downloading it from the main site, but instead it gives one headakes.

Erik






___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel