libRTI-NG.so.1 should be in test-tree/install/openrti/libRTI-NG.so.1

The following works for me:
------------------------------------------------
#bin/bash
TEST_TREE=$1
if [ "$TEST_TREE" == "" ]
then
        TEST_TREE="test-tree"
fi
mkdir -vp test-tree
cd test-tree
wget -c \
http://www.gitorious.org/fg/fgmeta/blobs/raw/master/download_and_compile.sh
sh download_and_compile.sh -j 2 |tee download_and_compile.sh--j-2.log
sh download_and_compile.sh -a n -p n -d n -j 2 ALL |tee \
download_and_compile.sh-a-n--p-n--d-n--j-2-ALL.log

run_fgrun.sh and Flightgear started right 


after the first  download_and_compile.sh, libRTI-NG.so.1 should be in
test-tree/install/openrti/libRTI-NG.so.1

A side note:
        $sh download_and_compile.sh. 
will work even without the chmod -x download_and_compile.sh

On Thu, 31 Jan 2013 07:25:39 +0100
Arnt Karlsen <a...@c2i.net> wrote:

> Hi,
> 
> ..has anyone tried testing FG build scripts in fresh trees?
> 
> ..as in, "mkdir -vp test-tree ;cd test-tree ;wget -c \
> http://www.gitorious.org/fg/fgmeta/blobs/raw/master/download_and_compile.sh
> ;chmod -x download_and_compile.sh  ;\
> sh download_and_compile.sh -a n -p n -d n -j 2 ALL ", like our recipe:
> http://wiki.flightgear.org/Scripted_Compilation_on_Linux_Debian/Ubuntu
> says is possible?  I get errors, the weird part is I can "prime" my
> test tree, and then most parts of download_and_compile.sh works, e.g.
> plib, openrti, OSG, SG and FG all builds ok, but FG bombs right out:
> ./run_fgfs.sh
> ./fgfs: error while loading shared libraries: libRTI-NG.so.1: cannot
> open shared object file: No such file or directory
> 
> 


------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to