On 12/21/06, Aleksey Y. Ulasevich (STAKANOV) wrote:

When I try to compile FGFS from CVS I see it:

...
Making all in Aircraft
make[2]: Entering directory `/home/pilot/FlightGear-0.9
/source/src/Aircraft'
if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src
-I/usr/local/include -I/usr/X11R6/include -g -O2 -D_REENTRANT -MT
aircraft.o -MD -MP -MF ".deps/aircraft.Tpo" -c -o aircraft.o aircraft.cxx;
\
then mv -f ".deps/aircraft.Tpo" ".deps/aircraft.Po"; else rm -f
".deps/aircraft.Tpo"; exit 1; fi
In file included from aircraft.cxx:44:
../../src/Model/acmodel.hxx:20:46: simgear/structure/ssgSharedPtr.hxx:
No such file or directory
In file included from aircraft.cxx:44:
../../src/Model/acmodel.hxx:47: error: ISO C++ forbids declaration of
`ssgSharedPtr' with no type
...


Slackware 11.0
SimGear 0.3 installed from CVS and I don't see
"simgear/structure/ssgSharedPtr.hxx" in /usr/local/include:

[EMAIL PROTECTED]:/usr/local/include/simgear/structure# ls
callback.hxx event_mgr.hxx SGReferenced.hxx subsystem_mgr.hxx
commands.hxx exception.hxx SGSharedPtr.hxx



When you build FlightGear from CVS you also need to first build and install
SimGear from CVS.  Then later, if you do a cvs update of one, you need to do
a cvs update of the other.  The two projects advance together.

Regards,

Curt.
--
Curtis Olson - University of Minnesota - FlightGear Project
http://baron.flightgear.org/~curt/  http://www.humanfirst.umn.edu/
http://www.flightgear.org
Unique text: 2f585eeea02e2c79d7b1d8c4963bae2d
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to