Re: [Flightgear-devel] download_and_compile.sh - version 1.9.12 finally ready
Geoff, Thanks for testing this. I left a set -x on line 371 which causes the double output you're seeing on -h. I've removed it. Also, I've changes the svn for plib to http://svn.code.sf.net/p/plib/code/trunk/. OSG and PLIB are slated for different treatment in a future version. If the chosen version of OSG, or the 1.8.5 version of PLIB is installed or previously built, there's no reason to reconfigure or rebuild them. In general, I'd like to be able to detect when git does not add a file to the sources. Then I could condition the configure step on whether its actually needed or not. If I find a way to do that quickly, it could be applied to any component that uses git, not just OSG. I'll be using your approach for plib at least. The latest is still 1.9.12: https://www.gitorious.org/fg/fg-download-and-compile-fgmeta/raw/master:download_and_compile.sh -Pat On Thu, 10 Oct 2013 12:50:15 +0200 Geoff McLane ubu...@geoffair.info wrote: Hi Pat, Finally got a chance to try download_and_compile.sh 1.9.12 from the ...-fgmeta repo... I think you need to adjust the svn repo for plib! It has permanently changed I think About ln 649 svn $PLIB_STABLE_REVISION_ co http://plib.svn.sourceforge.net/svnroot/plib/trunk/ plib to the new repo svn $PLIB_STABLE_REVISION_ co http://svn.code.sf.net/p/plib/code/trunk plib Also, as a suggestion, why not first search the system for an installed plib, and use that rather than a new download and compile? These days I have add plib as a 'system' install... In my makefg, which as you know was based on one of Brisa's original versions, circa Jan 2009, I use script like - # if NO plib installed path from user, and none from # previous configuration file, then if [ -z $INSTALL_DIR_PLIB ]; then # try the 'system' places PLIB_PATH=/usr if [ -f $PLIB_PATH/include/plib/ul.h ]; then show_plib_version $PLIB_PATH PLIB_INSTALL_OK=1 elif [ -f $PLIB_PATH/local/include/plib/ul.h ]; then show_plib_version $PLIB_PATH/local PLIB_INSTALL_OK=1 else PLIB_PATH= fi fi The function 'show_plib_version' just reads the version from the ul.h header... Anyway, just a suggestion... After the above svn correction, the script ran to the end, building fgcom, fgfs, fgrun, openrti, OpenSceneGraph, plib, simgear... great stuff... I only had a chance to try it with the ALL option ;=)) But found out later that is not really 'ALL'. I could add FGX, FGO?, FGCOMGUI, ATLAS and DATA, but I have already done the DATA separately overnight... I will try to get around to trying the others... presently doing -p FGX, but it insists on rebuilding OSG which is slow... One little thing. When I say run it with the -h help option for example my bash shell echos the echo lines, like the script has say - echo Switches: -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60134071iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] download_and_compile.sh - version 1.9.12 finally ready
Version 1.9.12 will build 2.10.0 as stable with -s, next without the -s 2.12.0 with -B release/2.12.0 master with -B master can someone do a final check on https://www.gitorious.org/fg/fg-download-and-compile-fgmeta/raw/6516d8db2c0ab3cf19722b5d3aa49e2860b6cf9b:download_and_compile.sh i've built each of the above and run the resulting flightgear I'd like to have someone besides me test it before we go ahead with the merge to the main fgmeta archive. Also, there's another version coming right after this that builds 2.12.0 as stable -Pat Here's the complete release notes: Version 1.9.12 release version of 1.9.12 function write_log() added. write_log writes summary information to sysout and a summary log file the function is added as a preview of changes to the logging for the script function SET_WINDOW_TITLE() changes the window title to indicate what is being built. function check_build() writes to the summary log a list of what was found as executables after a build. outputs a rebuild command the rebuild command can be used to re-execute the same build without entry of options or parameters. removes fgcomgui from the list of modules built when ALL is specified STOP_AFTER_ONE_MODULE Adds options z, B, R and G option z will set this so that only one module will be built, and then the script will immediately stop. This is useful during testing of the script. Option B allows the build of a specific branch. Without the R option it will build the head of the branch. option R allows the build of a specific revision or commit. Option G allows selection of a specific version of OpenSceneGraph. This version introduces the use of a bash associative array to select branch and version for building. patches allow building with fltk under Ubuntu 13.04 Open radar has been added -- LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/22/13. http://pubads.g.doubleclick.net/gampad/clk?id=64545871iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Download_and_compile.sh
James and Francesco, Proposal: The version of the script on the official fgmeta next, master and the upcoming release branch and should be maintained and should work. The same script version can be on each of these branches. Currently master does not work. next thinks stable is 2.8.0. Note that this message is not a request to merge, just a proposal for how to operate going forward. Right now in the official fgmeta, we have: fgmeta script script the script branch version status builds: -- --- -- -- next: 1.9.10 (working) next and 2.8.0 master 1.9.4 (not working) 2.12.0 1.9.10 (working) next and 2.8.0 2.10.0 1.9.4 (not working) in the fgmeta team clone we have: next: 1.9.tbd working but next, master, 2.12.0, not fully 2.10.0 2.8.0 tested OSG: 3.0.1 and any other named branch of OSG master 1.9.11 not releasednext and 2.8.0 untested minor changes Suggestion: backport the changes in 1.9.tbd that allows builds of next,master, 2.12.0, 2.10.0 etc to script version 1.9.11, test it and release it on Francesco's approval. or we could just fix 1.9.10 Thoughts? -Pat PS. You may be asking how big a change would it be to allow the script to build basically any branch, tag or commit# Not too bad: -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Download_and_compile.sh
On 20 Jul 2013, at 15:06, Pat pat.callah...@gmail.com wrote: Eventually I'd like to have a maintainable version on each branch. What we have in fgmeta master and fgmeta 2.10.0 is script version 1.9.4 The one on 2.8.0 is even older, 1.31. None of these work, mostly because of the osg svn url change and maybe other things. Someone would have to test to find out. Script version 1.9.10 which is currently on next does work as is for next and 2.8.0. You could merge that version back to master and the download_and_compile.sh instructions on the wiki will work again. I can backport the -B and -V options from the new script to a 1.9.11 based on 2.10.0. This minor change would mean the existing script could support next/master, 2.12.0, 2.10.0, 2.8.0 and maybe even 2.6.0. Let me know if you want me to do that. To be honest I'm not sure. In general, we don't touch the branches for prior releases (although of course we could). Of course the versions on master and next need to be kept up-to-date. Personally I don't see any value in encouraging people to run older versions of the sim; if people experience problems with newer versions, I'd far rather they reported that than kept using 2.6 or 2.8. There may be valid reasons to stick with a particular version for a dedicated project or similar, but for the kind of users download-and-compile is aimed at, supporting the current and previous stable releases seems sufficient to me. (Possibly as a Mac user my opinion on this is a little distorted!) However, download_and_compile is a little special, in that it supports multiple versions in a single file, so if you can create a compatible version with some small tweaks, then go for it, I guess. I would expect, ideally, that the version on master would build the current official release by default, and the versions on release/2.12.0 and next would build that explicit release, and next, by default respectively. Hopefully this is a one line change in the script when branching fgmeta? James -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Download_and_compile.sh
James and Francesco, Proposal: The version of the script on the official fgmeta next, master and the upcoming release branch and should be maintained and should work. The same script version can be on each of these branches. Currently master does not work. next thinks stable is 2.8.0. Note that this message is not a request to merge, just a proposal for how to operate going forward. Right now in the official fgmeta, we have: fgmeta script script the script branch version status builds: -- --- -- -- next: 1.9.10 (working) next and 2.8.0 master 1.9.4 (not working) 2.12.0 1.9.10 (working) next and 2.8.0 2.10.0 1.9.4 (not working) in the fgmeta team clone we have: next: 1.9.tbd working but next, master, 2.12.0, not fully 2.10.0 2.8.0 tested OSG: 3.0.1 and any other named branch of OSG master 1.9.11 not releasednext and 2.8.0 untested minor changes Suggestion: backport the changes in 1.9.tbd that allows builds of next,master, 2.12.0, 2.10.0 etc to script version 1.9.11, test it and release it on Francesco's approval. or we could just fix 1.9.10 Thoughts? -Pat PS. You may be asking how big a change would it be to allow the script to build basically any branch, tag or commit# Not too bad: -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Download_and_compile.sh
James, Eventually I'd like to have a maintainable version on each branch. What we have in fgmeta master and fgmeta 2.10.0 is script version 1.9.4 The one on 2.8.0 is even older, 1.31. None of these work, mostly because of the osg svn url change and maybe other things. Someone would have to test to find out. Script version 1.9.10 which is currently on next does work as is for next and 2.8.0. You could merge that version back to master and the download_and_compile.sh instructions on the wiki will work again. I can backport the -B and -V options from the new script to a 1.9.11 based on 2.10.0. This minor change would mean the existing script could support next/master, 2.12.0, 2.10.0, 2.8.0 and maybe even 2.6.0. Let me know if you want me to do that. -Pat BTW - it would obviously be nice to have this file in sync with the rest of the 2.12 release. James -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Download_and_compile.sh
An updated version of Download_and_compile.sh is available with numerous changes. without specifying version it will build next. -s builds 2.8.0. It can also build 2.12.0, 2.10.0 and 2.8.0, or any other branch, tag or commit. (-B and -V options.) -D 1 will use a more efficient directory structure.m-G lets you choose a different version of OSG. You can download it from the download_and_compile.sh team share:. https://www.gitorious.org/+fg-download-and-compile/fg/fg-download-and-compile-fgmeta/blobs/next/download_and_compile.sh The changes are numerous and significant. Francesco Brisa, the maintainer of download_and_compile.sh has not reviewed the changes so this remains on the tean repo for now. I'm using this version on a regular basis, but I need others to test this version and give feedback before I'll ask Francesco to approve it. Please let me know if you'd like to help. -Pat -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Download_and_compile.sh
good job put, yesterday I received my new PC, so I have a fully new fast pc to test it on :-) In August I will have plenty of time to further help. My best compliments to Pat ! 2013/7/18 Pat pat.callah...@gmail.com An updated version of Download_and_compile.sh is available with numerous changes. without specifying version it will build next. -s builds 2.8.0. It can also build 2.12.0, 2.10.0 and 2.8.0, or any other branch, tag or commit. (-B and -V options.) -D 1 will use a more efficient directory structure.m-G lets you choose a different version of OSG. You can download it from the download_and_compile.sh team share:. https://www.gitorious.org/+fg-download-and-compile/fg/fg-download-and-compile-fgmeta/blobs/next/download_and_compile.sh The changes are numerous and significant. Francesco Brisa, the maintainer of download_and_compile.sh has not reviewed the changes so this remains on the tean repo for now. I'm using this version on a regular basis, but I need others to test this version and give feedback before I'll ask Francesco to approve it. Please let me know if you'd like to help. -Pat -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Download_and_compile.sh
On 18 Jul 2013, at 12:45, Pat pat.callah...@gmail.com wrote: Francesco Brisa, the maintainer of download_and_compile.sh has not reviewed the changes so this remains on the tean repo for now. I'm using this version on a regular basis, but I need others to test this version and give feedback before I'll ask Francesco to approve it. Please let me know if you'd like to help. I'm happy to merge this is into fgmeta's 2.12 branch once it has had some testing, BTW - it would obviously be nice to have this file in sync with the rest of the 2.12 release. James-- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] download_and_compile.sh and CMake Superbuild discussion
Pat Callahan and James Turner had an irc converation today about building flightgear. Here is Pat's summary of the main points Ongoing changes to Download_and_compile.sh Pat's goal is to increase the functionality of the script without changing the way it is used for simple builds of master/next or stable builds. these changes can be seen on the team clone Pat is using for download_and_compile.sh maintenance. Let Pat or Francesco know if you want to join the team in any capacity. https://www.gitorious.org/+fg-download-and-compile/fg/fg-download-and-compile-fgmeta The changes on the team clone are pretested, but may still contain bugs. 1.9.10 is very well tested. 1.9.11 is ready for has only minor changes. next has had some testing but could use a serious workout. Francisco will approve all changes that are to be merged with the main fgmeta tree. Francesco has approved 1.9.10 and 1.9.11 for merging into the master fgmeta tree, but has yet to see and approve next next has additional details on pat's future versions beyond next starting at line 54. download_and_compile.sh version number: James thought the version numbers for download_and_compile might be confusing. They're different from the versions for flightgear. Pat thinks we could put a working version on each branch that is tested to work with that specific branch, with a version number to match the flightgear version on the branch. We might want to make a rule that next should always support next, master and the previous 2 releases. Pat will bring the script version issue up with Francesco. The cmake superbuild: James thought that a cmake superbuild could do most if not all of the basic functions of the script. Pat likes the idea and thinks it can be integrated with the script or used independently. The superbuild approach could be used without a script to do a simple build on any platform, while download_and_compile.sh wuld provide additional options not easily provided by cmake. If the superbuild had enough additional logic built into it it could also do more complex and more efficient build scenarios and could be the build engine for most flightgear components in download_and_compile.sh James goal of a simple build method for any platform would still be met. The additonal logic and variables in the CMakeLists.txt would be there, but most users would never need to examine it. Basic Instructions should look something like this: wget \ http://www.gitorious.org/fg/fgmeta/blobs/raw/next/CMakeLists.txt cmake -D.FGVERSION=2.10.0 ./ make The cmake file is incomplete at this point, and this build fails to install because its trying to use /usr/local/lib/i386-linux-gnu without admin privs -Pat -- How ServiceNow helps IT people transform IT departments: 1. A cloud service to automate IT design, transition and operations 2. Dashboards that offer high-level views of enterprise services 3. A single system of record for all IT processes http://p.sf.net/sfu/servicenow-d2d-j ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] download_and_compile.sh one git repository or serveral.
On Mon, 25 Feb 2013 12:19:54 +0100 Stefan Seifert n...@detonation.org wrote: On Sunday 24 February 2013 22:18:05 Pat wrote: Anders made a suggestion on IRC I'm going to follow up on. You can have local git clones that share the same .git/* files via file links ..you feed 4 build trees from 1 git clone, how? A du -sch $git-n-build-trees on them all? - Arnt You probably don't want to symlink all the files in .git. You just want to symlink the objects subdirectory. This is the place where all the real data is and it would be the same for all local repositories. The other files list for example branches and tags and very important: the currently checked out branch. So if you want several local repositories with different branches checked out, you may not share these files. snip Stefan Thanks! With the one above, and one each from Anders and James, I now have three good suggestions with two alternative new approaches to look into. However this may all be moot unless the new approaches save considerable time and effort down the road. I'm not sure they would so I'm not going to pursue them at this time. My original purpose was to avoid cloning from git for each test build. I'm using download and compile.sh to create builds for several sets of option combinations. Do this for more than one version and you end up with more than enough complete copies of git to satisfy an army of coders. This wastes bandwidth on gitorious. I'm thinking that one local git for each version (next, master, maint 2.10.0 ) is simple enough. Its four copies of git but that's not too bad... I can make change to the script to allow concurrent separate builds with different options off these separate gits without too much change. The single git method could come later if anyone thinks it's worth doing. -Pat -- 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_feb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] download_and_compile.sh one git repository or serveral.
I thought there would be a benefit to moving fgdata out from under
${CBD}/install. Currently, if you do mulitple builds with different
options in different folders, you end up with multiple copies of the
same version of fgdata, even though a related build has a perfectly
good copy.
I've got it set up like this:
build/
download_and_compile.sh
fgdata-2.11.0
fgdata
fgdata-2.10.0
fgdata
master
install
fgfs
fgdata symlink
stable
install
fgfs
fgdata symlink
stable-e
install
fgfs
fgdata symlink
stable-ei
etc.
I'm trying this out and will send a patch when its working right.
-Pat
--
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_feb
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] download_and_compile.sh one git repository or serveral.
patch-1.9-8-xv.patch adds the x and v options for debugging. patch-1.9-8-w.patch adds the w option, w standing for Where to Build patch-1.9-8-wxv.patch combines both changes. ..alongside those, I like to see _what_ I build|t _when_, so I auto-rename my logs, and I believe -s should build 2.10 now: arnt@celsius:~/FG-git$ ll download_and_compile-1.9-8a.patch \ md5sum download_and_compile-1.9-8a.patch -rw-r--r-- 1 arnt arnt 1441 Feb 24 23:24 download_and_compile-1.9-8a.patch a342d108f121322f076ef7de063ab1e4 download_and_compile-1.9-8a.patch arnt@celsius:~/FG-git$ how about two types of logging: 1. Timestamped record of the start,finish and status of each run 2. full log with logrotate feature Anders made a suggestion on IRC I'm going to follow up on. You can have local git clones that share the same .git/* files via file links ..you feed 4 build trees from 1 git clone, how? A du -sch $git-n-build-trees on them all? I'm just learning how to work with git, one baby step at a time. I'm sure the suggestion is valid. My interpretation of it may not be. From what I'm reading its possible to have multiple source trees working off one git repository. You'd do the git operations as usual. Again, I'm not sure how all this works but I'm learning. Does anyone have a script for something like this for any application? I think that means we could have several local clones of a single local git repository. The various local clones would support building multiple branches and versions, without having to sync each clone independently with gitorious. ..you only do an e.g. git branch 2.10 ;git checkout, and no git pull??? Its a good bet the usual git operations will apply. Thanks Pat There's an old joke about a city guy asking a farmer how to get to a nearby town. The farmer looks at him with a straight face and replies You can't get there from here. I'm the city guy. -- 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_feb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] download_and_compile.sh one git repository or serveral.
On Sunday 24 February 2013 22:18:05 Pat wrote: Anders made a suggestion on IRC I'm going to follow up on. You can have local git clones that share the same .git/* files via file links ..you feed 4 build trees from 1 git clone, how? A du -sch $git-n-build-trees on them all? You probably don't want to symlink all the files in .git. You just want to symlink the objects subdirectory. This is the place where all the real data is and it would be the same for all local repositories. The other files list for example branches and tags and very important: the currently checked out branch. So if you want several local repositories with different branches checked out, you may not share these files. So in essence, you have one plain normal clone of the repository: git clone git://... fg-master For the other repositories, you could set them up like: # create a local clone (no download) git clone fg-master fg-whatever # copy the config of master so both use gitorious as remote cp fg-master/.git/config fg-whatever/.git/config # replace objects in the clone by the symlink rm -Rf fg-whatever/.git/objects ln -s fg-master fg-whatever/.git/objects Repeat these steps for all the branches you want to test. This gives you several local clones of the repository which can have different branches checked out and which share the meat of the repository data. You can work in them just like in any normal repository. Just do the usual git pull / git checkout / ... When you do git pull, git will download new objects and then merge the remote into the local branch. It should not matter in which branch you download the new objects since git does not change old ones. Just don't do any history changing like git rebase. ..you only do an e.g. git branch 2.10 ;git checkout, Btw. the shortcut would be just: git checkout -b 2.10 creates the branch and checks it out. Stefan signature.asc Description: This is a digitally signed message part. -- 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_feb___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] download_and_compile.sh one git repository or serveral.
On Sun, 24 Feb 2013, Pat wrote: Anders made a suggestion on IRC I'm going to follow up on. You can have local git clones that share the same .git/* files via file links ..you feed 4 build trees from 1 git clone, how? A du -sch $git-n-build-trees on them all? I'm just learning how to work with git, one baby step at a time. I'm sure the suggestion is valid. My interpretation of it may not be. What you want to do is a --local clone, e.g.: git clone --local ~/FlightGear/build/SimGear/simgear.git It creates hard links between the (or some) .git/* files in the new and origin repositories. It only works if both are on the same file system. I'm not sure if the repositories continue to share (new) changes when these are fetched from upstream. If not you need to run git fetch or git pull in first the local origin repository and then in the clone(s) to propagate new changes. Cheers, Anders -- --- Anders Gidenstam WWW: http://gitorious.org/anders-hangar http://www.gidenstam.org/FlightGear/ -- 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_feb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] download_and_compile.sh one git repository or serveral.
On 25 Feb 2013, at 14:54, Anders Gidenstam anders-...@gidenstam.org wrote: What you want to do is a --local clone, e.g.: git clone --local ~/FlightGear/build/SimGear/simgear.git It creates hard links between the (or some) .git/* files in the new and origin repositories. It only works if both are on the same file system. I'm not sure if the repositories continue to share (new) changes when these are fetched from upstream. If not you need to run git fetch or git pull in first the local origin repository and then in the clone(s) to propagate new changes. Yet another option is: http://stackoverflow.com/questions/6270193/multiple-working-directories-with-git Which was also mentioned on IRC - I've tried it with other projects and it works just fine, but need a little bit of care, especially avoid having the same branch live in both working directories. Essentially it automates creating the links described above. James -- 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_feb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] download_and_compile.sh
I've been learning a lot about Linux development by reading the download_and_compile.sh. I have a few ideas for enhancements to the script. Is anyone keeping a list of requested enhancements to the script? Is this list the right place for discussion of the script and changes to it? -Pat -- 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_nov ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] download_and_compile.sh
On 12.11.2012 14:25, Pat wrote: I've been learning a lot about Linux development by reading the download_and_compile.sh. I have a few ideas for enhancements to the script. Is anyone keeping a list of requested enhancements to the script? Is this list the right place for discussion of the script and changes to it? The script is maintained by Francesco Brisa. Not sure if he's reading this list. Otherwise try contacting him directly (see contact details in script header). cheers, Thorsten -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] download_and_compile.sh
Yes, reading :-) 2012/11/12 ThorstenB bre...@gmail.com On 12.11.2012 14:25, Pat wrote: I've been learning a lot about Linux development by reading the download_and_compile.sh. I have a few ideas for enhancements to the script. Is anyone keeping a list of requested enhancements to the script? Is this list the right place for discussion of the script and changes to it? The script is maintained by Francesco Brisa. Not sure if he's reading this list. Otherwise try contacting him directly (see contact details in script header). cheers, Thorsten -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] download_and_compile.sh script link
On Fri, 15 Apr 2011 15:20:58 +0200, Geoff wrote in message 1302873658.8552.1.camel@DELL02: Hi Arnt, http://geoffair.org/tmp/makefg ..idea for makefg-1.3.0: WEUSESYSTEMPLIB=1, WEUSESYSTEMOSG=1 Already thought of, and done ;=)) ..aha, I was in an hurry and wondering a wee bit too much about all these newfangled complexities since last time. ;oD For all the recent versions there are options - PLIBPATH=path OSGPATH=path ..these would point to libplib-dev and libopenscenegraph-dev for building, and to libplib1 and libopenscenegraph71 at run-time? Or are we static enough to stay with *-dev fire-'n-forget style? arnt@celsius:~/FG-git$ dpkg -l |grep plib |fmt -tu ii ftplib3 3.1-1-8 Library of callable ftp routines ii libplib-dev 1.8.5-5 Portability Libraries: Development package ii libplib-doc 1:1.8.5-3 Portability Libraries: documentation and examples ii libplib1 1.8.5-5 Portability Libraries: Run-time package ii python-httplib2 0.6.0-4 comprehensive HTTP client library written for Python arnt@celsius:~/FG-git$ dpkg -l |grep openscene |fmt -tu ii libopenscenegraph-dev 2.9.11-1 3D scene graph, development files ii libopenscenegraph65 2.8.3-7 3D scene graph, shared libs ii libopenscenegraph71 2.9.11-1 3D scene graph, shared libs ii openscenegraph 2.9.11-1 3D scene graph, utilities and examples (binaries) ii openscenegraph-doc 2.9.11-1 3D scene graph, documentation ii openscenegraph-examples 2.9.11-1 3D scene graph, examples (sources) arnt@celsius:~/FG-git$ Which should do what you ask, but I have NEVER installed PLIB nor OSG into a 'standard' system path, so have never tried these options in that case, but they should work... That is why the only relevant thing I get is 'openal' when I run things like - for i in openal plib openscene simgear \ flightgear ; do dpkg -l |grep $i ;done |fmt -tu ..the output please, so we know I understand your openal story. ;o) I have used, and tested them when I do _NOT_ want to download and build yet another of these 2, thus when building in say ~/fg/fg14, I can reuse say my builds in ~/fg/fg12/install/[plib|osgvers]... And likewise there are options - BOOSTPATH=path BOOSTLIBS=path to point to where BOOST is either installed or 'staged' (not built or installed)... ..and they are set once makefg finds boost? And a very, _VERY_ important one these days :- FGDATADIR=path to _NOT_ re-clone this massive block multiple times ;=)) time and space... ..amen, does it default to install/fgfs/fgdata, I see makefg suggesting build/fgfs/fgdata ??? However, at present you have to do MANUAL updates of such sources if the path is outside the 'root' build... and I think it will stay that way... As you may have learned, once a build completes successfully, some 'configuration' information is written to ~/bin/makefg-version.conf file, so you do _NOT_ have to remember to re-input such paths when it is run again, again, and again... ..I have now, like I said, I was wondering a wee bit too much. ;o) Of course, with care you can manually adjust this 'conf' file... but it is easy to mess up the simple parsing that is done... so not particularly recommended ;=() ..we'll find out. ;o) And that is why there is a option NO_CONF, to tell the script to ignore any 'configuration' file information, when you want to really 'change' the setup drastically... Lots of options ;=)) over 80-90 at last count... Regards, Geoff. ..means we have around 80! to 90! new ways to crash 'n burn in the back-to-the-drawing-board routine. ;o) -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...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. -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] download_and_compile.sh script link
Hi Arnt, http://geoffair.org/tmp/makefg ..idea for makefg-1.3.0: WEUSESYSTEMPLIB=1, WEUSESYSTEMOSG=1 Already thought of, and done ;=)) For all the recent versions there are options - PLIBPATH=path OSGPATH=path Which should do what you ask, but I have NEVER installed PLIB nor OSG into a 'standard' system path, so have never tried these options in that case, but they should work... That is why the only relevant thing I get is 'openal' when I run things like - for i in openal plib openscene simgear \ flightgear ; do dpkg -l |grep $i ;done |fmt -tu I have used, and tested them when I do _NOT_ want to download and build yet another of these 2, thus when building in say ~/fg/fg14, I can reuse say my builds in ~/fg/fg12/install/[plib|osgvers]... And likewise there are options - BOOSTPATH=path BOOSTLIBS=path to point to where BOOST is either installed or 'staged' (not built or installed)... And a very, _VERY_ important one these days :- FGDATADIR=path to _NOT_ re-clone this massive block multiple times ;=)) time and space... However, at present you have to do MANUAL updates of such sources if the path is outside the 'root' build... and I think it will stay that way... As you may have learned, once a build completes successfully, some 'configuration' information is written to ~/bin/makefg-version.conf file, so you do _NOT_ have to remember to re-input such paths when it is run again, again, and again... Of course, with care you can manually adjust this 'conf' file... but it is easy to mess up the simple parsing that is done... so not particularly recommended ;=() And that is why there is a option NO_CONF, to tell the script to ignore any 'configuration' file information, when you want to really 'change' the setup drastically... Lots of options ;=)) over 80-90 at last count... Regards, Geoff. -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] download_and_compile.sh script link
Hi Arnt, http://geoffair.org/tmp/makefg ..your makef|tg is still version 1.2.3, Geoff? That link should be to 1.2.4 IIRC. And have not used/changed the 'tg' version for _MANY_ months, but also think it should be 1.2.4... Am presently testing a makefg 1.2.5, especially using an OSGTRUNK switch, and while SG/FG compiled and linked fine, I can not get fgfs to run - (a) The status text on the splash is 'broken', and (b) it 'aborts' some short time after the output - loading scenario 'nimitz_demo' sg/fg/fgdata are a git pull of today... and naturally include SGCLEAN and FGCLEAN to do a FULL re-build... Still researching the cause(s) ;=(( like add log debug, and running under gdb, but may revert to OSG 283 or 299 soon, to see if that gets me back to a 'working' version before withdrawal sets in ;=)) Regards, Geoff. -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] download_and_compile.sh script link
On Thu, 14 Apr 2011 18:51:45 +0200, Geoff wrote in message 1302799905.6456.2.camel@DELL02: Hi Arnt, http://geoffair.org/tmp/makefg ..your makef|tg is still version 1.2.3, Geoff? That link should be to 1.2.4 IIRC. And have not used/changed the 'tg' version for _MANY_ months, but also think it should be 1.2.4... Am presently testing a makefg 1.2.5, especially using an OSGTRUNK switch, and while SG/FG compiled and linked fine, I can not get fgfs to run - ..url to makefg-1.2.5RC0? ..this still fits in dropping the data into the same places as Francesco's download_and_compile.sh? (I'm tight on disk space and funding.) (a) The status text on the splash is 'broken', and (b) it 'aborts' some short time after the output - loading scenario 'nimitz_demo' sg/fg/fgdata are a git pull of today... and naturally include SGCLEAN and FGCLEAN to do a FULL re-build... Still researching the cause(s) ;=(( like add log debug, and running under gdb, but may revert to OSG 283 or 299 ..both 2.9.10 and 2.9.11 fails for you? soon, to see if that gets me back to a 'working' version before withdrawal sets in ;=)) ..can't have that happening. ;o) -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...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. -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] download_and_compile.sh script link
Hi Arnt, http://geoffair.org/tmp/makefg This is 'now' 1.2.5, since I am quite happy with it so far... but still testing... But specific version are usually also available under their version numbers - http://geoffair.org/tmp/makefg-1.2.5 http://geoffair.org/tmp/makefg-1.2.4 http://geoffair.org/tmp/makefg-1.2.3 etc... Have not specifically checked Brisa's script, but yes, in the main I use the 'same' directory structure, as per his 'original' script. But you could check, and adjust that... And yes, with the ever growing size of fgdata I too am coming in for a bit of disk squeeze ;=)) Normally I keep the previous say ~/fg/fg14, and move to a new folder, ~/fg/fg15, but... ..both 2.9.10 and 2.9.11 fails for you? Never tried 2.9.10, but had trouble with 2.9.11 last time I tried, months ago, both in Ubuntu, and WIN32 XP... My re-build of sg/sg back with OSG 2.8.3 just complete, grace of a simple script command - ~/fg/fg14$ makefg OSG283 FGCONF FGCLEAN SGCONF SGCLEAN NOPAUSE NO_CONF and so far it RUNS JUST FINE ;=)) Phew, the 'shakes' were starting... The script also supports OSG299, but think I have had enough of a 'fright' for a while ;=)) Need some quiet flying time... Regards, Geoff. -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] download_and_compile.sh script link
On Thu, 14 Apr 2011 20:24:50 +0200, Geoff wrote in message 1302805490.6456.10.camel@DELL02: Hi Arnt, http://geoffair.org/tmp/makefg This is 'now' 1.2.5, since I am quite happy with it so far... but still testing... But specific version are usually also available under their version numbers - http://geoffair.org/tmp/makefg-1.2.5 http://geoffair.org/tmp/makefg-1.2.4 http://geoffair.org/tmp/makefg-1.2.3 etc... Have not specifically checked Brisa's script, but yes, in the main I use the 'same' directory structure, as per his 'original' script. But you could check, and adjust that... And yes, with the ever growing size of fgdata I too am coming in for a bit of disk squeeze ;=)) Normally I keep the previous say ~/fg/fg14, and move to a new folder, ~/fg/fg15, but... ..both 2.9.10 and 2.9.11 fails for you? Never tried 2.9.10, but had trouble with 2.9.11 last time I tried, months ago, both in Ubuntu, and WIN32 XP... My re-build of sg/sg back with OSG 2.8.3 just complete, grace of a simple script command - ~/fg/fg14$ makefg OSG283 FGCONF FGCLEAN SGCONF SGCLEAN NOPAUSE NO_CONF and so far it RUNS JUST FINE ;=)) Phew, the 'shakes' were starting... The script also supports OSG299, but think I have ..idea for makefg-1.3.0: WEUSESYSTEMPLIB=1, WEUSESYSTEMOSG=1 etc, printing the warning to standard output and pointing the build to whatever is installed on the box, I did something similar on my last building on Francesco's former script: https://github.com/gasguru/flightgearthings/blob/master/download_and_compile.sh-1.2.0-sysOSG he has since released a newer version. had enough of a 'fright' for a while ;=)) Need some quiet flying time... ..aaaye, I'd like that kinda boredom too. :o) -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...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. -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] download_and_compile.sh script link
Hi I saw that in the wiki page the link to the download_and_compile.sh script has been moved to gitorious, which is good, but, in the last weeks I have done some fixes to the script to let it compile with new changes in simgear/osg etc How can I update the script on gitorious ? for example some changes are to use osg 2.8.3 as default (Always use stabel version) since last versions does not compile with simgear. btw, last script version is here: http://assistenza.larasrl.net/brisa/fgfs/download_and_compile.sh Cheers Francesco -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] download_and_compile.sh script link
On Mon, 11 Apr 2011 12:13:52 +0200, Francesco wrote in message BANLkTim=UdKQg=7=4ktdvmoehfqnscd...@mail.gmail.com: Hi I saw that in the wiki page the link to the download_and_compile.sh script has been moved to gitorious, which is good, but, in the last weeks I have done some fixes to the script to let it compile with new changes in simgear/osg etc How can I update the script on gitorious ? for example some changes are to use osg 2.8.3 as default (Always use stabel version) since last versions does not compile with simgear. ..is osg-2.8.3 compatible with the latest shaders on ATI cards? btw, last script version is here: http://assistenza.larasrl.net/brisa/fgfs/download_and_compile.sh Cheers Francesco ..thanks. -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...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. -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] download_and_compile.sh script link
Am 11.04.11 13:29, schrieb Arnt Karlsen: rsion) since last versions does not compile with simgear. ..is osg-2.8.3 compatible with the latest shaders on ATI cards? Latest *stable release* of OSG is 2.8.3 (bug/build fix release). Latest *developer release* is OSG 2.9.11, released on 28th January 2011 As far as I know sg/fg runs with stable OSG 2.8.3, or dev release 2.9.7, some say also with dev release 2.9.9, and some other say also with dev release 2.9.11. The hudson builds use 2.9.9 for simgear-next (but this is no reference, it compiles all with this version, does not say there are no issues). Cheers, Yves -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] download_and_compile.sh script link
Hi Francesco, Good to see your post... Re: download_and_compile.sh Thank you, thank you, and thank you for your scripts ;=)) It was, and _IS_, the basis of my own script, 'makefg', http://geoffair.org/tmp/makefg in which I acknowledge your script, and your script continues to be one of my 'references'... BUT, could you please 'bump' the version number, which seems 'stuck' at :- VERSION=1.2 For those of us who continue to 'monitor' your script changes, I for one would appreciate knowing the 'latest' version number, like say 1.2.1, .2, .3, etc... Further, you now give a NEW link to your latest script, http://assistenza.larasrl.net/brisa/fgfs/script so perhaps you could also correct the 'link' given inside the script of - http://brisa.homelinux.net which for me, no longer seems to function ;=(( While, as you point out, using OSG-2.8.3 stable will ALWAYS works, and I know OSG-2.9.9 also works, recent posts indicate OSG-trunk will _ALSO_ compile, but I have yet to fully personally 'verify' this... But perhaps this should be a user 'option' to the script... Again, thank you for sharing such a 'powerful', all inclusive script. Be the user be a 'power' user, or a casual sg/fg 'git' builder, such a script is _VERY_ useful, at the very least, just to see the ideas of others... In answer to your specific question - How can I update the script on gitorious ? As I understand it :- (a) you have to be awarded 'maintainer' status to directly 'push' a change to gitorious, or (b) you can register on gitorious/fg, and create a merger request, and wait for a 'maintainer' to do the necessary 'merge', or (c) simply wait for other 'maintainers' to pick up your changes, at their desire, convenience... Again, thanks for continuing your script efforts... always VERY MUCH appreciated... Regards, Geoff. -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] download_and_compile.sh script link
On Mon, 11 Apr 2011 13:44:11 +0200, HB-GRAL wrote in message 4da2e98b.7090...@sablonier.ch: Am 11.04.11 13:29, schrieb Arnt Karlsen: rsion) since last versions does not compile with simgear. ..is osg-2.8.3 compatible with the latest shaders on ATI cards? ..yes, no, work-in-progress or dunno? ;o) Latest *stable release* of OSG is 2.8.3 (bug/build fix release). Latest *developer release* ..this is s|fg-git-next? And s|fg-git-master is the *stable release*? is OSG 2.9.11, released on 28th January 2011 ..and in use with Debian Sid+Experimental, I guess Sid is 2.9.9, Alex, can you verify? As far as I know sg/fg runs with stable OSG 2.8.3, or dev release 2.9.7, some say also with dev release 2.9.9, and some other say also with dev release 2.9.11. The hudson builds use 2.9.9 for simgear-next (but this is no reference, it compiles all with this version, does not say there are no issues). ..well, we're here to find out. ;o) How much more disk space does s|fg-git-next need to shoe-horn into my s|fg-git-master tree? -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...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. -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] download_and_compile.sh script link
Am Mon, 11 Apr 2011 12:13:52 +0200 schrieb Francesco Angelo Brisa fbr...@gmail.com: for example some changes are to use osg 2.8.3 as default (Always use stabel version) since last versions does not compile with simgear. Ahoy Brisa, a few weeks ago I startet some testing with different versions of OSG on FG git 'next' and 'releases/2.2.0'. Version 2.8.3, the first one to test, turned out to seg fault FG quite often. More of them on two days than the 6 months before that test. I used the version from the Debian [1] repo and did not compile it myself. After that I decided to find the newest developer release that works properly here. Atm. I am using 2.9.10 [2] which seems to be pretty stable. With version 2.9.11 and newer there are, at least, issues with OsgText. System: ATI Technologies Inc RS880 [Radeon HD 4200] Catalyst 10.11 and 11.2 used during testing Kernel: 2.6.32-5-amd64 [1] Debian GNU/Linux Stable 6.x (Squeeze); libopenscenegraph-dev 2.8.3-5 [2] svn co http://www.openscenegraph.org/svn/osg/OpenSceneGraph/tags/OpenSceneGraph-2.9.10 Alex 8-) -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] download_and_compile.sh script link
2011/4/11 Geoff McLane ubu...@geoffair.info Hi Francesco, Good to see your post... Re: download_and_compile.sh Thank you, thank you, and thank you for your scripts ;=)) happy to see that the script is usefull to you ! It was, and _IS_, the basis of my own script, 'makefg', http://geoffair.org/tmp/makefg in which I acknowledge your script, and your script continues to be one of my 'references'... BUT, could you please 'bump' the version number, which seems 'stuck' at :- VERSION=1.2 it is not stuck, it is that somebody else was updating the version number to 1.2 in the git repo, while mine was still at 1.1 now I updated at 1.2 and the version numbers are equal, but different scripts... For those of us who continue to 'monitor' your script changes, I for one would appreciate knowing the 'latest' version number, like say 1.2.1, .2, .3, etc... Further, you now give a NEW link to your latest script, http://assistenza.larasrl.net/brisa/fgfs/script so perhaps you could also correct the 'link' given inside the script of - http://brisa.homelinux.net which for me, no longer seems to function ;=(( While, as you point out, using OSG-2.8.3 stable will ALWAYS works, and I know OSG-2.9.9 also works, recent posts indicate OSG-trunk will _ALSO_ compile, but I have yet to fully personally 'verify' this... But perhaps this should be a user 'option' to the script... Again, thank you for sharing such a 'powerful', all inclusive script. Be the user be a 'power' user, or a casual sg/fg 'git' builder, such a script is _VERY_ useful, at the very least, just to see the ideas of others... In answer to your specific question - How can I update the script on gitorious ? As I understand it :- (a) you have to be awarded 'maintainer' status to directly 'push' a change to gitorious, or (b) you can register on gitorious/fg, and create a merger request, and wait for a 'maintainer' to do the necessary 'merge', or (c) simply wait for other 'maintainers' to pick up your changes, at their desire, convenience... thanks for answer. I will check for option B Again, thanks for continuing your script efforts... always VERY MUCH appreciated... Regards, Geoff. Cheers Francesco -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] download_and_compile.sh script link
2011/4/11 Alex D-HUND f...@beggabaur.de Am Mon, 11 Apr 2011 12:13:52 +0200 schrieb Francesco Angelo Brisa fbr...@gmail.com: for example some changes are to use osg 2.8.3 as default (Always use stabel version) since last versions does not compile with simgear. Ahoy Brisa, Hi D-HUND ! a few weeks ago I startet some testing with different versions of OSG on FG git 'next' and 'releases/2.2.0'. Version 2.8.3, the first one to test, turned out to seg fault FG quite often. More of them on two days than the 6 months before that test. I used the version from the Debian [1] repo and did not compile it myself. After that I decided to find the newest developer release that works properly here. Atm. I am using 2.9.10 [2] which seems to be pretty stable. With version 2.9.11 and newer there are, at least, issues with OsgText. well ,I will make some experiments on 2.9.10 if it finds out to compile easly and to be quite stable, I will make it the default behaviour, with 2.8.3 as stable option. System: ATI Technologies Inc RS880 [Radeon HD 4200] Catalyst 10.11 and 11.2 used during testing Kernel: 2.6.32-5-amd64 [1] Debian GNU/Linux Stable 6.x (Squeeze); libopenscenegraph-dev 2.8.3-5 [2] svn co http://www.openscenegraph.org/svn/osg/OpenSceneGraph/tags/OpenSceneGraph-2.9.10 Alex 8-) Cheers Francesco -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] download_and_compile.sh script link
On 11.04.2011 17:29, Francesco Angelo Brisa wrote: well ,I will make some experiments on 2.9.10 if it finds out to compile easly and to be quite stable, I will make it the default behaviour, with 2.8.3 as stable option. When we last discussed this (February), 2.9.9 was reported to be stable with FlightGear on all three platforms (Linux/Mac/Windows) with fg/next - no issues were reported since. But meanwhile we've updated FlightGear to also support the latest OSG interface (= 2.9.10). Concerning the OSGText issue, there is also a bug tracker entry on this: http://code.google.com/p/flightgear-bugs/issues/detail?id=268 We don't know if OSG 2.9.10 is also affected - or only = 2.9.11. Would be good if someone could verify. While, as you point out, using OSG-2.8.3 stable will ALWAYS works, and I know OSG-2.9.9 also works, recent posts indicate OSG-trunk will _ALSO_ compile, but I have yet to fully personally 'verify' this... But perhaps this should be a user 'option' to the script... Well, OSG-trunk compiles - today. If an option to use OSG-trunk is really necessary (is it?), then please hide it well enough so that normal users won't find it. :) cheers, Thorsten -- Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010 Forrester Wave Report as part of an in-depth evaluation of disaster recovery service providers. Forrester found the best-in-class provider in terms of services and vision. Read this report now! http://p.sf.net/sfu/ibm-webcastpromo ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] download_and_compile.sh script link
On Mon, 11 Apr 2011 20:59:09 +0200, ThorstenB wrote in message 4da34f7d.7040...@gmail.com: On 11.04.2011 17:29, Francesco Angelo Brisa wrote: well ,I will make some experiments on 2.9.10 if it finds out to compile easly and to be quite stable, I will make it the default behaviour, with 2.8.3 as stable option. When we last discussed this (February), 2.9.9 was reported to be stable with FlightGear on all three platforms (Linux/Mac/Windows) with fg/next - no issues were reported since. But meanwhile we've updated FlightGear to also support the latest OSG interface (= 2.9.10). Concerning the OSGText issue, there is also a bug tracker entry on this: http://code.google.com/p/flightgear-bugs/issues/detail?id=268 We don't know if OSG 2.9.10 is also affected - or only = 2.9.11. Would be good if someone could verify. ..I confirm I saw the same random letters in the splash screen with Debian Sid+Experimental osg-2.9.11-1 and S|FG-git master on Debian Sid+Experimental and X.org's radeon driver. While, as you point out, using OSG-2.8.3 stable will ALWAYS works, and I know OSG-2.9.9 also works, recent posts indicate OSG-trunk will _ALSO_ compile, but I have yet to fully personally 'verify' this... But perhaps this should be a user 'option' to the script... Well, OSG-trunk compiles - today. If an option to use OSG-trunk is really necessary (is it?), then please hide it well enough so that normal users won't find it. :) ..no, use them to flog OSG to fix their own (OSG's) bugs. ;o) ..we _are_ sure this (#268) is OSG's bug and not ours? ..I keep hearing how newer gcc versions issue more and more pedantic warnings, precisely to help weed out the old bugs. -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...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. -- Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010 Forrester Wave Report as part of an in-depth evaluation of disaster recovery service providers. Forrester found the best-in-class provider in terms of services and vision. Read this report now! http://p.sf.net/sfu/ibm-webcastpromo ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] download_and_compile.sh script link
On Mon, 11 Apr 2011 15:53:59 +0200, Geoff wrote in message 1302530039.6696.5.camel@DELL02: Hi Francesco, Good to see your post... Re: download_and_compile.sh Thank you, thank you, and thank you for your scripts ;=)) It was, and _IS_, the basis of my own script, 'makefg', http://geoffair.org/tmp/makefg in which I acknowledge your script, and your script continues to be one of my 'references'... BUT, could you please 'bump' the version number, which seems 'stuck' at :- VERSION=1.2 For those of us who continue to 'monitor' your script changes, I for one would appreciate knowing the 'latest' version number, like say 1.2.1, .2, .3, etc... ..I used to append an a to Geoff's version number, a g should for for him? ;o) ..your makef|tg is still version 1.2.3, Geoff? Further, you now give a NEW link to your latest script, http://assistenza.larasrl.net/brisa/fgfs/script so perhaps you could also correct the 'link' given inside the script of - http://brisa.homelinux.net which for me, no longer seems to function ;=(( While, as you point out, using OSG-2.8.3 stable will ALWAYS works, and I know OSG-2.9.9 also works, recent posts indicate OSG-trunk will _ALSO_ compile, but I have yet to fully personally 'verify' this... But perhaps this should be a user 'option' to the script... Again, thank you for sharing such a 'powerful', all inclusive script. Be the user be a 'power' user, or a casual sg/fg 'git' builder, such a script is _VERY_ useful, at the very least, just to see the ideas of others... ..aye, I'd also like to see time stamps, git revisions and compiler version used etc in the log output, helps answer any developer question, ideally without delays. In answer to your specific question - How can I update the script on gitorious ? As I understand it :- (a) you have to be awarded 'maintainer' status to directly 'push' a change to gitorious, or (b) you can register on gitorious/fg, and create a merger request, and wait for a 'maintainer' to do the necessary 'merge', or (c) simply wait for other 'maintainers' to pick up your changes, at their desire, convenience... Again, thanks for continuing your script efforts... always VERY MUCH appreciated... Regards, Geoff. ..hear, hear. :o) -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...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. -- Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010 Forrester Wave Report as part of an in-depth evaluation of disaster recovery service providers. Forrester found the best-in-class provider in terms of services and vision. Read this report now! http://p.sf.net/sfu/ibm-webcastpromo ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
