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 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? 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. 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 ;=)) 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 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>/install/fgfs/bin 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. 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... > ..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... I use a set of <CURRENT WORK>, like fg1, fg2, fg3, etc which I can run, trash or keep depending on my fancy ;=)) I am quite 'happy' with 'makes' update and dependence senses, thus no need for 'other' tools to help in this. 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... Regards, Geoff. ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
