I used the download_and_compile.sh script as described here:
http://wiki.flightgear.org/Scripted_Compilation_on_Linux_Debian/Ubuntu.
I have done this all under my home directory under a "flightsim"
directory I made, and my system is
$ cat /etc/issue
Ubuntu 11.04
$ uname -a
Linux software1 2.6.38-10-generic #46-Ubuntu SMP Tue Jun 28 15:07:17 UTC
2011 x86_64 x86_64 x86_64 GNU/Linux
First off, those instructions seem to say to run the script with no
arguments, and it will download and compile everything. Then "sh
run_fgfs.sh" or "sh run_fgrun.sh" should immediately work. Those shell
scripts weren't there unless I re-ran the script with added arguments.
I've tried FGRUN (which seemed to help that one shell script to show
up), DATA, and ALL.
When I then do "sh run_fgrun.sh" it pops up a window titled FlightGear
Wizard, and subtitled Select Paths, however, the Next button is greyed
out. There are directories pre-filled in for Executable, FG_ROOT,
FG_SCENERY, and (a file for) Airports Cache. There is nothing
pre-filled for FG_AIRCRAFT nor Terrasync exe, and I don't know what to
put there, and I don't know if it is those missing, or some other
problem, that is greying out the Next button. I googled a bit and it
seems one would normally point FG_AIRCRAFT to "FGROOT/Aircraft" but I
don't know where that is supposed to be in this download_and_compile
folder structure. The only Aircraft folder I have, at least within the
"flightsim" folder heirarchy is fgfs/flightgear/src/Aircraft but it
looks more like code, not data:
CMakeLists.txt controls.hxx libAircraft.a Makefile.am replay.cxx
replay.o
controls.cxx controls.o Makefile Makefile.in replay.hxx
I also have separately installed FlightGear via the package manager, so
I tried pointing FG_AIRCRAFT at what appears to be the Aircraft
directory, /usr/share/games/FlightGear/Aircraft, however this did not
help in the sense that the Next button is still greyed out.
Also when I guessed at what to put for the terrasync exe spot, which I
found in ~/flightsim/install/fgfs/bin/terrasync, the Next button is
still greyed out.
I also tried this without using run_fgrun, but just using fgrun:
$ cd ~/flightsim/install/fgrun/bin
$ ./fgrun
./fgrun: error while loading shared libraries: libosgParticle.so.66:
cannot open shared object file: No such file or directory
$
I also tried without using
$ cd ~/flightsim/install/fgfs/bin
$ ./fgfs
./fgfs: error while loading shared libraries: libosgFX.so.66: cannot
open shared object file: No such file or directory
Are these problems with the download_and_compile.sh script? or with the
instructions on that wiki page? or with something I'm doing?
Thank you for any tips.
Martin
p.s. the download_and_compile seemed to finish without errors, unless
the "you asked me to pull without telling me which branch..." message is
an error that I should know how to correct.
$ sh download_and_compile.sh ALL
PLIB
...
At revision 2166.
...
OSG
...
Checked out revision 12741.
...
SIMGEAR
...
simgear exists already.
Already up-to-date.
...
FGFS
...
make[3]: Nothing to be done for `install-exec-am'.
make[3]: Nothing to be done for `install-data-am'.
make[3]: Leaving directory
`/home/mmuc/flight.simulator/fgfs/flightgear/utils/propmerge'
make[2]: Leaving directory
`/home/mmuc/flight.simulator/fgfs/flightgear/utils/propmerge'
Making install in fgviewer
make[2]: Entering directory
`/home/mmuc/flight.simulator/fgfs/flightgear/utils/fgviewer'
make[3]: Entering directory
`/home/mmuc/flight.simulator/fgfs/flightgear/utils/fgviewer'
test -z "/home/mmuc/flight.simulator/install/fgfs/bin" || /bin/mkdir -p
"/home/mmuc/flight.simulator/install/fgfs/bin"
/usr/bin/install -c -p fgviewer
'/home/mmuc/flight.simulator/install/fgfs/bin'
make[3]: Nothing to be done for `install-data-am'.
make[3]: Leaving directory
`/home/mmuc/flight.simulator/fgfs/flightgear/utils/fgviewer'
make[2]: Leaving directory
`/home/mmuc/flight.simulator/fgfs/flightgear/utils/fgviewer'
Making install in fgpanel
make[2]: Entering directory
`/home/mmuc/flight.simulator/fgfs/flightgear/utils/fgpanel'
make[3]: Entering directory
`/home/mmuc/flight.simulator/fgfs/flightgear/utils/fgpanel'
test -z "/home/mmuc/flight.simulator/install/fgfs/bin" || /bin/mkdir -p
"/home/mmuc/flight.simulator/install/fgfs/bin"
make[3]: Nothing to be done for `install-data-am'.
make[3]: Leaving directory
`/home/mmuc/flight.simulator/fgfs/flightgear/utils/fgpanel'
make[2]: Leaving directory
`/home/mmuc/flight.simulator/fgfs/flightgear/utils/fgpanel'
make[2]: Entering directory
`/home/mmuc/flight.simulator/fgfs/flightgear/utils'
make[3]: Entering directory
`/home/mmuc/flight.simulator/fgfs/flightgear/utils'
make[3]: Nothing to be done for `install-exec-am'.
make[3]: Nothing to be done for `install-data-am'.
make[3]: Leaving directory
`/home/mmuc/flight.simulator/fgfs/flightgear/utils'
make[2]: Leaving directory
`/home/mmuc/flight.simulator/fgfs/flightgear/utils'
make[1]: Leaving directory
`/home/mmuc/flight.simulator/fgfs/flightgear/utils'
make[1]: Entering directory `/home/mmuc/flight.simulator/fgfs/flightgear'
make[2]: Entering directory `/home/mmuc/flight.simulator/fgfs/flightgear'
make[2]: Nothing to be done for `install-exec-am'.
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/home/mmuc/flight.simulator/fgfs/flightgear'
make[1]: Leaving directory `/home/mmuc/flight.simulator/fgfs/flightgear'
You asked me to pull without telling me which branch you
want to merge with, and 'branch.master.merge' in
your configuration file does not tell me, either. Please
specify which branch you want to use on the command line and
try again (e.g. 'git pull <repository> <refspec>').
See git-pull(1) for details.
If you often merge with the same branch, you may want to
use something like the following in your configuration file:
[branch "master"]
remote = <nickname>
merge = <remote-ref>
[remote "<nickname>"]
url = <url>
fetch = <refspec>
See git-config(1) for details.
$
------------------------------------------------------------------------------
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
The must-attend event for mobile developers. Connect with experts.
Get tools for creating Super Apps. See the latest technologies.
Sessions, hands-on labs, demos & much more. Register early & save!
http://p.sf.net/sfu/rim-blackberry-1
_______________________________________________
Flightgear-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
