> >When compiling SimGear 0.0.16 with the latest Cygwin (Win2K) I get the
> >following compiler error. Has anyone else seen this? This is
> >a "clean"
> >SimGear with ./configure; make.
> >
> >Everything goes well until...
> >
> >Making all in simgear/metakit/unix
>
> This is getting repetitive
David Megginson wrote:
>
> Using a hash_map might speed things up as well.
>
hash_map istn't a STL standard and shouldn't be used (IIRC).
CU,
Christian
--
The idea is to die young as late as possible.-- Ashley Montague
Whoever that is/was; (c) by Douglas Adams would have been better.
Erik Hofman wrote:
> Do you have any idea if the mmap() function is available on all
> platforms? This is basically like a one shot read of the airports file
> into memory (but instead leaving it on the drive). It would be easy to
> search the memory location then.
Bad idea. This means that
> David Megginson writes:
> >
> >I think that mmap is Unix only; in any case,
>
> Windows certainly has a mmap equivalent
> in fact one could almost say that Win9X is a 'mmap hack'
>
Windows has the CreateFileMapping call and several other
functions to map a file into memory.
-Fred
___
David Megginson writes:
>
>I think that mmap is Unix only; in any case,
Windows certainly has a mmap equivalent
in fact one could almost say that Win9X is a 'mmap hack'
Cheers
Norman
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.fl
David Megginson writes:
>
>Curtis L. Olson writes:
>
> > This can significantly increase load times ... which is a hassle if
> > you are doing a lot of compile/run testing ...
>
>I just wrote a short ANSI C++ test program to read the airport
>database from the text file into an in-memory hash tabl
Erik Hofman writes:
> > I just wrote a short ANSI C++ test program to read the airport
> > database from the text file into an in-memory hash table. The basic
>
> Do you have any idea if the mmap() function is available on all
> platforms? This is basically like a one shot read of the air
David Megginson wrote:
> Curtis L. Olson writes:
>
> > This can significantly increase load times ... which is a hassle if
> > you are doing a lot of compile/run testing ...
>
> I just wrote a short ANSI C++ test program to read the airport
> database from the text file into an in-memory hash
Curtis L. Olson writes:
> This can significantly increase load times ... which is a hassle if
> you are doing a lot of compile/run testing ...
I just wrote a short ANSI C++ test program to read the airport
database from the text file into an in-memory hash table. The basic
data structures loo
Curtis L. Olson wrote:
>>
>>How about turning over to a "real" SQL database:
>>http://www.hwaci.com/sw/sqlite/
>>
>
> Well, our needs are very simple, and likely any package will have it's
> share of headaches. I'd prefer just working through the metakit
> issues rather than picking another pa
"Curtis L. Olson" wrote:
>
> BERNDT, JON S. (JON) (JSC-EX) (LM) writes:
> > What is MetaKit, anyhow?
>
> Metakit is a lightweight, simple, embedable database library. We use
> it to store key/value pairs on disk (airport id vs. the airport info
> for instance.) It can take several seconds (mor
Curtis L. Olson writes:
>Norman Vine writes:
>>
>> Fine but ...
>> Just remember that in general we want to DECREASE the number of
>> files that need to be opened per tile as fopen() is a
>'major' contributor
>> to the ' SIM stuttering' when loading a tile on some systems !
>
>Oooo, , oh w
BERNDT, JON S. (JON) (JSC-EX) (LM) writes:
> What is MetaKit, anyhow?
Metakit is a lightweight, simple, embedable database library. We use
it to store key/value pairs on disk (airport id vs. the airport info
for instance.) It can take several seconds (more on some slower disk
subsystems) to loa
Erik Hofman writes:
> Curtis L. Olson wrote:
>
>
> >
> > Do you know if this change will work ok on other platforms, why does
> > it help? I don't recall anyone submitting this patch to me before,
> > but I've got about 850 pending messages in my flightgear inbox so it
> > could still be in th
Norman Vine writes:
> David Megginson writes:
> >
> >Curtis L. Olson writes:
> >
> > > Getting metakit to build properly from within SimGear has been a PITA
> > > from day one. Right now I'm voting for de-bundling it.
> >
> >I say yank it completely and either (a) store all of the data in
> >mem
Norman Vine writes:
> Curtis L. Olson writes:
> >
> Getting metakit to build properly from within SimGear has been a PITA
> from day one. Right now I'm voting for de-bundling it.
>
> Whatever
>
> I do notice that the flags in the Makefile.in are not those I suggest
>
> http://www.menet.umn.ed
David Megginson writes:
> I say yank it completely and either (a) store all of the data in
> memory,
This can significantly increase load times ... which is a hassle if
you are doing a lot of compile/run testing ...
> or (b) split it into directories like the scenery data. The airport
> and nav
Norman Vine wrote:
> Erik Hofman writes:
>>Eh, no.
>>I need the CXXFLAGS from SimGear in Metakit.
>>
>
> AH AH !
>
> Is this only for a specific compiler or Machine type
Yep. IRIX.
> Can you tell me how to identify your machine(s) that need the
> SimGear CXXFLAGS because they BREAK compi
Curtis L. Olson wrote:
>
> Do you know if this change will work ok on other platforms, why does
> it help? I don't recall anyone submitting this patch to me before,
> but I've got about 850 pending messages in my flightgear inbox so it
> could still be in there ... it helps me if patches come
What is MetaKit, anyhow?
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
David Megginson writes:
>
>Curtis L. Olson writes:
>
> > Getting metakit to build properly from within SimGear has been a PITA
> > from day one. Right now I'm voting for de-bundling it.
>
>I say yank it completely and either (a) store all of the data in
>memory, or (b) split it into directories
Erik Hofman writes:
>Norman Vine wrote:
>
>>
>> # not normally compiled with -g, but you can specify it in
>the make command
>> CXXFLAGS = -O3 -fomit-frame-pointer -DNDEBUG
>> #CXXFLAGS = -fguiding-decls -Wall -pedantic -Wno-unused -g
>> #CXXFLAGS = @CXXFLAGS@ -DNDEBUG
>> >
>Eh, no.
>I need the
Curtis L. Olson writes:
>
Getting metakit to build properly from within SimGear has been a PITA
from day one. Right now I'm voting for de-bundling it.
Whatever
I do notice that the flags in the Makefile.in are not those I suggest
http://www.menet.umn.edu/~curt/lists/fgfs/archive-200104/msg006
Norman Vine wrote:
> Paul Deppe
>
>>When compiling SimGear 0.0.16 with the latest Cygwin (Win2K) I get the
>>following compiler error. Has anyone else seen this? This is
>>a "clean"
>>SimGear with ./configure; make.
>>
>>Everything goes well until...
>>
>>Making all in simgear/metakit/unix
>>
Curtis L. Olson writes:
> Getting metakit to build properly from within SimGear has been a PITA
> from day one. Right now I'm voting for de-bundling it. Most linux
> users could just install the metakit package for their distro. Norman
> could probably talk it into cygwin if it's not there
Norman Vine writes:
> Curtis L. Olson writes:
> >
> >Norman Vine writes:
> >>
> >> This is getting repetitive
> >>
> >> Would someone who has SimGear CVS write privlidge
> >> PLEASE change the CXXFLAGS variable in
> >>
> >> SimGear/simgear/metakit/unix/Makefile.in to
> >>
> >> # not normally c
Curtis L. Olson writes:
>
>Norman Vine writes:
>>
>> This is getting repetitive
>>
>> Would someone who has SimGear CVS write privlidge
>> PLEASE change the CXXFLAGS variable in
>>
>> SimGear/simgear/metakit/unix/Makefile.in to
>>
>> # not normally compiled with -g, but you can specify it in
Norman Vine writes:
> Paul Deppe
> >When compiling SimGear 0.0.16 with the latest Cygwin (Win2K) I get the
> >following compiler error. Has anyone else seen this? This is
> >a "clean"
> >SimGear with ./configure; make.
> >
> >Everything goes well until...
> >
> >Making all in simgear/metakit/un
Jon S. Berndt writes:
>
>> Paul Deppe wrote:
>
>> > When compiling SimGear 0.0.16 with the latest Cygwin
>(Win2K) I get the
>> > following compiler error. Has anyone else seen this?
>This is a "clean"
>> > SimGear with ./configure; make.
>> >
>> > Everything goes well until...
>
>I've got Cyg
Paul Deppe
>When compiling SimGear 0.0.16 with the latest Cygwin (Win2K) I get the
>following compiler error. Has anyone else seen this? This is
>a "clean"
>SimGear with ./configure; make.
>
>Everything goes well until...
>
>Making all in simgear/metakit/unix
This is getting repetitive
Would
> Paul Deppe wrote:
> > When compiling SimGear 0.0.16 with the latest Cygwin (Win2K) I get the
> > following compiler error. Has anyone else seen this? This is a "clean"
> > SimGear with ./configure; make.
> >
> > Everything goes well until...
I've got CygWin (pretty much the latest, I think)
Paul Deppe wrote:
> Gents,
>
> When compiling SimGear 0.0.16 with the latest Cygwin (Win2K) I get the
> following compiler error. Has anyone else seen this? This is a "clean"
> SimGear with ./configure; make.
>
> Everything goes well until...
>
> Making all in simgear/metakit/unix
> make[1]:
Gents,
When compiling SimGear 0.0.16 with the latest Cygwin (Win2K) I get the
following compiler error. Has anyone else seen this? This is a "clean"
SimGear with ./configure; make.
Everything goes well until...
Making all in simgear/metakit/unix
make[1]: Entering directory
`/home/fgfs_sw/SimG
33 matches
Mail list logo
