Ross Golder writes:

> I've committed the beginnings of an auto* system to OpenGC CVS. I've
> tidied up all the problems I can, but my build system isn't complete yet,
> so YMMV. It should all run from the 'autogen.sh' script. Let me know if
> you have any problems.
>
Okay, I downloaded the CVS modules and started a test build.
aclocal - OK

automake -a  At some point we will need to create the INSTALL, README,
AUTHORS files for automake..

autoconf -OK

./configure - OK

make - bombed. the ogcFontManager is looking for the include files for the
gltt  library. (See ogcFont.h)

(For some inane reason we have been unable to set up my developer account,
so I had to stop) Perhaps that is just as well regards the make system;
Something about too many cooks.... So I'll serve as the beta tester and post
the problems.

Might see a few on the horizon; for example,
 1)there is no _itoa(...) method in ANSI C++,  MSVC provides a lib function,
but had to create an ogc_itoa(...) and build it into the ogcFontManager
module and library.

 2)had a problem with the template ogcOrderedPair and "typename" changed
typename to class, it compiles and runs but... will this present a problem
later on?

 3) have been unable to commit the ogcFGDataSource code to CVS. (See above
on account setup)

 4) it might make sense to create a build system that allows for individual
display panels. There would be one for the PDF, ND, EICAS, CDU. Each would
run as a separate app.

 5) I sent Curtis some source that makes changes to FG and isolates
(insulates) the network interface to OpenGC and requires only changes to an
opengc.hxx and display.[ch]xx that defines the data packet across the
interface. Once those are incorporated it would make sense to remove the
Opengc-Unix tar file to prevent the proliferation of  "unofficial" copies.

Once we get my developer account set up, I'll commit the source for the
interface and a preliminary EICAS module.

Regards
John W.


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

Reply via email to