-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi Geoff, >On Fri, 17 Apr 2009 10:23:24 -0300 Geoff McLane <ubu...@geoffair.info> wrote: > >It seems you have installed PLIB, OpenSceneGraph (OSG), >simgear, simgear-cs, etc into the 'global' environment, >that is the 'standard' install situation, and then >dealt with the obvious clash between cvs >simgear, and git simgear-cs libraries... >As an alternative, I only install plib, OSG, cvs-SG, >git-SG, etc, relative to the build directory by careful >use of --prefix=<path> during the ./configure >stage. Yes, I tend to install most (all) packages in a 'global' fashion, since this is a single-user machine. Also for the reason that if certain packages or libs are ever wanted by some other software at a later date, I don't need to have multiple installations of them for each application that needs them. As an example, the Fast-Light Toolkit (fltk), required by one of the external FG components (FGCON if I recall) is already on my system as I needed that for something long ago. The only real difference between mine and maybe a typical multi- user linux system as far as install locations, is I try to avoid installing to /usr/local and instead as you noted I install to /usr. I find this more organized & consistent. In the cases of these FG/TG packages & deps, I actually built and 'installed' them into an arbitrary local folder (instead of directly into the system) using either $DESTDIR or --prefix= and then manually constructed a Slack-package of that folder using Slackware's makepkg utility. Finally, I use Slackware's installpkg utility to install my finished package into the system. It's a slightly klunky way of doing things, but I have become frustrated with the otherwise excellent (unofficial slackware package maker) src2pkg lately: with each new version release of src2pkg, it is _increasingly_ automated (read: intelligent), and thus _decreasingly_ flexible, and is difficult to use with the wide variety of non-standard sourcecode needed by the FG/TG apps. >So I, and some others, have some do-it-all scripts >to achieve this :- >seb : > http://seb.marque.free.fr/fichiers/scripts/bash/compile.tgz >Francesco : >http://wiki.flightgear.org/index.php/Scripted_Compilation_on_Linux_ >Debian/Ubuntu >and mine, based on that by Francesco - now version 1.0.9 > http://geoffair.net/tmp/makefg >- plib,osg,sg(cvs),fg(cvs),fgrun,data - opt Atlas > http://geoffair.net/tmp/maketg >- plib,osg,sg(git),tg(git),data > >You just create a new folder in your user space, >like say tg, and run the script - >~$ md tg >~$ cd tg >~/tg$ ./maketg > >Note, it is run WITHOUT 'sudo', and as a 'user', >not 'root', and on the initial run, it does require your >pwd to do apt-get install <long list> of packages, >and tools... I will definitely be looking at these and other links you have provided. For the record though, and FYI to others, Slackware (11.0 at least) does not come by default with SUDO installed/enabled, nor does it use APT or a comparable Debian-like package/dependency manager. Slack- packages are .tgz archives, source is (usually) tar.gz or tar.bz2 archives, and any dependencies are managed by the administrator/user. >Now onto the scenery, the purpose of the >TG tools ;=)) With this suite of TG tools available, >you may want to take a look at my :- > http://geoffair.net/tmp/makeCYYT >script. This builds St John, but it would >not be too much trouble to adapt it to >build Nova Scotia (CYHZ)... >And I have a developing page detailing some of >the 'fun' building scenery :- > http://geoffair.net/tmp/newscenery.htm >which will at sometime be moved to my FG >sub-web... and has some other reference links >near the bottom... Excellent :) I will definitely be looking at these pages very soon!! Questions: 1) On the subj. of scenery, what is the current status of FG/TG as far as being able to deal with vmap1 and/or otherwise more highly detailed topographic data? Is it limited to 3-arcsec or 30-arcsec data, or *could* I attempt to build more detailed scenery than is recomended, using vmap1 and/or 1-arcsec data? (At least for my own use in accordance with the idea that the default downloadable data archive for FG should be usable my the largest segment of the public, though if it worked I would happily upload my completed scenery to somewhere if/when that time comes). 2) Is this mailing-list accepting subscriptions? Should I subscribe? Thanks very much for your timely and helpful feedback, and have FUN indeed :) Sasha -----BEGIN PGP SIGNATURE----- Charset: iso-8859-1 Note: This signature can be verified at https://www.hushtools.com/verify Version: Hush 3.0 wpwEAQMCAAYFAknong0ACgkQBdgPeajIhBkTVgQAgPdcbVPcbXSA4InHZI5Rp+L2bXFa PgRpp1Nv/VLR5KTA+ToCir5yA8ueauXhYxWB9Otjr6cwJ1XJm0vB7r7SA8xvxYdVi251 JTMuynEVRW8Xo3lSauJYnPuaNjrTxBV6Yold+C64UV2MsF2LhPfwYWCZHPhJxefPn4Lv ZVs8gYA= =pjbP -----END PGP SIGNATURE----- -- Easy-to-use, advanced features, flexible phone systems. Click here for more info. http://tagline.hushmail.com/fc/BLSrjkqmC5wbnSMyh8Y6y25YNzszcM67V8w6sqoPUuzkJUbK1TAtzj1j7tW/ ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ Flightgear-users mailing list Flightgear-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-users
