On Wed, 18 Mar 2009 19:45:06 +0100, Arnt wrote in message <20090318194506.4214f...@a45.fmb.no>:
> On Wed, 18 Mar 2009 19:10:27 +0100, Geoff wrote in message > <1237399827.6663.78.ca...@dell02>: > > > Hi Arnt, > > > > Have just copied up version 1.0.5, which tries to > > get around the 'shell' question... > > > > Get these, and _DELETE_ all others... > > http://geoffair.net/tmp/maketg > > http://geoffair.net/tmp/makefg > > ..got it, I'll first try a ./maketg NOPAUSE DOUPD to chk > if it sees plib, your 1.0.4 and my 1.0.4a didn't. ;o) > > > Version 1.0.5 Changes - > > 1 - version number and date, of course... > > 2 - package and tool update separated into several > > 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. ..if everything needed is on board, there's no need to sudo. ..that said, there _is_ a use for build-time throw-away build tools, which could warrant KEEP-BUILD-TIME-TOOLS and THROW-AWAY-BUILD-TIME-TOOLS switches, e.g. tool and distro release etc debugging. ..running as root in $HOME or anything owned by $USER, should throw an error, in the Debian etc world, we do "sudo aptitude install fakeroot ;man fakeroot ". ;o) > > 3 - A work around for a standard shell (sh) that > > does not substitute echo "\t" to a TAB, 0x09, > > needed in the Makefile... > > 4 - a new switch, OSGNOUPD, to be used with DOUPD, > > that updates everything EXCEPT OSG, due to the > > time it takes for the OSG compile. ..sweet, I was thinking in terms of a STOP-TO-PATCH-TG switch or a patch tree. > > The work around tries to 'test' if > > echo "\t" produces an 0x09, and if NOT, tries > > echo -e "\t", and puts out noisy warnings if > > this second attempt fails also... and says > > you should do the Makefile MANUALLY ;=)) .."Oh Horror!!!". ;o) > > Other items - > > > > 1. more shell expansion/substitution > > > > I have experimented with #!/bin/bash, but find that > > it definitely does NOT expand "\t" unless written as > > echo -e "\t", in my system. > > > > So the scripts have been left as #!/bin/sh, but I > > try to do a check if it is correctly substituting "\t" > > and if not, try using echo -e "\trm etc", as mentioned. > > > > In my system /bin/sh is actually just a link to > > /bin/dash... so, effectively #!/bin/dash should > > be no different to #!/bin/sh ..ln -s /bin/sh /bin/dash is standard Ubuntu practice? Debian uses Bash, and RH, SuSE, Mandrake etc I ever tried, all used Bash. > > 2. location of executables > > > > FG: Since I often have _MANY_ copies of this, > > with variations, changes, experiments, I > > do _NOT_ install this binary into any 'standard' > > location. > > > > So the scripts install this 'fgfs' exe into > > <CURRENT WORK> ..ok, why "." and $COMPILE_BASE_DIR and $CDB, and not "$PWD"??? > > /install/fgfs/bin ..which in maketg-1.0.5 is ./install/$/bin or $COMPILE_BASE_DIR/$INSTDIR/bin and could be $PWD/$INSTDIR/bin etc. > > and run_fgfs.sh (and run_fgrun.sh) scripts are written > > in <CURRENT WORK> to run this executable, together > > with the pointer to OSG shared libraries it needs. > > > > The other components, including the important > > OSG shared libraries are thus installed into > > <CURRENT WORK>/install/<component_name>/lib, include > > and/or bin, so they can be 'used' in the script in a > > 'known' location... > > > > TG: Because this is a suite of tools that > > I want access to from whatever <SCENERY WORK> > > directory I am in at the time, then these are > > all installed to a SINGLE location. As a location for > > this I have chosen - > > $HOME/bin > > since I add this to my 'standard' PATH. ..ok, and will be in /opt/bygg/install/<component_name>/bin etc in my 1.0.5a. > > 3. FG/TG trees > > > > In each <CURRENT WORK> I run BOTH makefg and maketg, > > since they share PLIB and OSG, and I use different directory > > names to separate cvs and git components... ..ah, :o) I can mv -vf to merge my /opt/bygg/*g trees. ;o) > > > ..is why I'd like to build throw-away .deb's. ;o) > > Have never built a .deb, although I understand it is > > some form of packaging... ..used in both Debian and its derivative Ubuntu, for your distro's FG .deb, you use "sudo apt-get install fgfs " etc. "Oh wait!" ;o) ..building things from source into .deb's, the Debian Way, also takes care of the dependencies. > > I use a set of <CURRENT WORK>, > > like fg1, fg2, fg3, etc which I can run, trash or keep depending > > on my fancy ;=)) ..aye, combining that idea with distro pack building and brlcad style binary naming, means we can do "accidental releases" on any cross-arch build that succeeds. ;o) > > I am quite 'happy' with 'makes' update and dependence > > senses, thus no need for 'other' tools to help in this. ..disagreed. ;o) > > The full compile time is just not that long, even if it > > does appear to sometimes needlessly re-compile certain things... > > > > And each component has a 'CLEAN' switch, like TGCLEAN, > > FGCLEAN, etc, to effectively start the full compile again... > > > > Anyway, hope these latest 1.0.5 work for you... ..thanks ;o), it still keeps on missing plib: "Doing TG ./configure --prefix=/home/arnt --exec-prefix=/home/arnt --with-osg=/opt/bygg/tg/install/OpenSceneGraph --with-simgear=/opt/bygg/tg/install/simgear-cs --with-plib=/opt/bygg/tg/install/plib ... checking for TIFFOpen in -ltiff... yes checking for ulInit in -lplibul... no checking how to run the C++ preprocessor... g++ -E checking plib/sg.h usability... no checking plib/sg.h presence... no checking for plib/sg.h... no You *must* have the plib library installed on your system to build TerraGear! Please see README.plib for more details. configure aborted." ..now trying 1.0.5a with $PWD/patches/terragear-cs.diff ;o) a...@a45:/opt/bygg/tg $ diff -U0 maketg-1.0.5 maketg --- maketg-1.0.5 2009-03-18 19:19:15.000000000 +0100 +++ maketg 2009-03-18 21:53:05.000000000 +0100 @@ -38 +38 @@ -SCVERSION="1.0.5" +SCVERSION="1.0.5a" @@ -244,2 +244,5 @@ -TG_INSTALL_DIR=$HOME -INSTALL_DIR_TG=$HOME +TG_INSTALL_DIR=$INSTALL_DIR/$TG_SOURCE_DIR +# $INSTALL_DIR/$TG_INSTALL_DIR +# $HOME +INSTALL_DIR_TG=$INSTALL_DIR/$TG_INSTALL_DIR +# $HOME > > Regards, > > > > Geoff. -- ..med vennlig hilsen = with Kind Regards from Arnt... ;o) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
