Re: [Flightgear-devel] maketg and makefg scripts

[Geoff M. <ub...@ge...>]

Hi Arnt,

Please reduce the unnecessary 'size' of your emails. Sometimes
it takes many clicks to get to anything you MAY have added.

Instead of adding _ALL_ that has been said, pick out a little
of the relevant context, if needed, like I do... ;=))

============
> > IT WILL NOT 'SEE' PLIB UNLESS YOU PATCH configure.ac as
> > detailed...
> ..ok, add a patches tree and PATCH-ALL and PATCH-* stanzas 
> to your make*g-1.0.6's? ;o)

Simple answer is NO! ;=)) I am expecting the patch to get
into the git terragear-cs sometime SOON - at least I HOPE
so... otherwise the current configure.ac will ONLY
support simgear, osg, plib installed into a 'standard'
path ;=((

So, NO, my scripts handle enough things already
without this type of HOPEFULLY TEMPORARY 'patch' addition...

And concerning DOUPD, this should ONLY be used AFTER
the initial downloads and builds are done, when you
really MEAN that you want a FULL update of everything.

That is _AFTER_ a full successful build, and some time has
passed. The scripts will always do the initial 
download/checkout/clone WITHOUT it...

In fact, they are meant to be run repeatedly WITHOUT any
parameters added. I do not even consider NOPAUSE a 'safe'
option!!! You SHOULD always at least inspect the ./configure
step results, and abort if something is MISSING...

And ADDDEBUG will write the ./configure output to the LOG file,
for even more careful inspection...

=============
> > /opt/bygg/fg/simgear/source/simgear/timing/timestamp.cxx:79:
> > undefined reference to `clock_gettime' 
> ..still happening with your makefg-1.0.5.

Not when I run it ;=()

I have NO IDEA why you get this error building fgfs.
Mine builds ok. You did not give enough output to know
exactly what was happening, but when linking fgfs, which
includes -lsgtiming, it also includes -lrt, which I think
is the library that contains this function.

~$ ls -l /lib/librt*
-rw-r--r-- 1 root root 35784 2008-09-12 16:15 /lib/librt-2.7.so
but not sure. Is there a command to sort of 'dump' a
library to know what it exports? That is dump an ascii export
list, not a 'hex' dump, like xxd?

But anyway, this does not show anything wrong with my makefg
script that I can see...

=============
> >   lines, since I found that sometimes using one
> >   LONG line of 'apt-get update a b c...' seemed to
> >   MISS some packages in the list!!! Not sure why?
> ..could be related to whining about sudo apt-get install 
> without (or before) chking whether those are necessary, 
> try $basename --version style chks or dpkg -l |grep what 
> ever your scripts needs. 

Again NO, it is NOT! In all my tests, it just seems to
'miss' some things in a long list of things, and never
'complains' about repeated invocations. I do not always
use NOPAUSE, and often READ the last outputs before
continuing... the reason the 'waits' were put there
in the first place!

Yes, something like dpkg -l | grep would also do it, but
that is even MORE scripting. Thus in a way, sudo apt-get
install 'item' _IS_ a simple check that the 'item' exists...

=============
> ..ln -s /bin/sh /bin/dash is standard Ubuntu practice?
~$ ls -l /bin/sh
lrwxrwxrwx 1 root root 4 2008-08-16 17:27 /bin/sh -> dash
Do not know if it is 'standard', but it is certainly done
on my system.

============
>From the list of TG executables, it seems you got these
built. PHEW!!! Of course you are 'free' to install them where
ever you like ;=)) just like you have done, amending
INSTALL_DIR_TG=<whatever/you/want>

Now comes the 'hard' part, and that is building scenery
using these tools... HAVE FUN ;=))

Regards,

Geoff.