Hi Curt,

> I apologize that this is less than obvious at the first crack, but
> simgear and flightgear are typically developed in parallel so you need
> to have a matched set.  SimGear-0.0.18 corresponds to
> FlightGear-0.7.10.  However if you want to build the cvs version of
> FlightGear, you also need the *cvs* version of SimGear.  See
> www.simgear.org for the details on how to checkout the latest simgear
> cvs code.

Sigh, well, no it wasn't.  hehe, watching me go through all this might
be useful for someone writing up a howto ;-).

Anyway, I went over to simgear and followed the directions verbatum
(copy/paste) and got more problems.  It isn't clear to me if I should
have used it as it stands or if I needed to add the version at the end:

 cvs -d :pserver:[EMAIL PROTECTED]:/var/cvs/SimGear-0.0 login

---------------------------------------------------------^^ (add .18?)

But taking it as that is what I should do (not adding version) I end up
with the following:

{/usr/local/src/SimGear} $  aclocal ; automake -a ; autoconf
automake: configure.in: installing `./install-sh'
automake: configure.in: installing `./mkinstalldirs'
automake: configure.in: installing `./missing'
automake: Makefile.am: installing `./INSTALL'
configure.in: 335: required file `simgear/simgear_config.h.in' not found

no it isn't there :-(.

:-), sigh, :-), This is going to be so fun once I get familiar with how
this is done and getting everything correct in place :-).

Any ideas where I am staggering around in the darkness here?

Thanks & take care, Vikki (only driven to drink vanilla coke so far :-).
-- 
Victoria Welch, WV9K/7, SysAdmin, Embedded Systems Designer.
"Walking on water and developing software to specification
are easy as long as both are frozen" - Edward V. Berard.
Do not unto others, that which you would not have others do unto you.
"Micro$oft Windows. I'll bet you can't install it just once!"


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

Reply via email to