date:20130218

Hi all,

I just wanted to let everyone know here that I created a PPA for
FlightGear on Launchpad and have compiled and uploaded FlightGear 2.10.0
for Oneiric and above. Unfortunately, the fgfs-base isn't available at
the moment, so users will have to download that separately. The link to
the PPA itself is
https://launchpad.net/~saiarcot895/+archive/flightgear. Users can follow
the following steps to use the PPA and flightgear:

1. Add ppa:saiarcot895/flightgear to their list of sources, either
using Software Sources or sudo add-apt-repository
ppa:saiarcot895/flightgear.
2. Do an update using apt-get update.
3. Either use Synaptic to install FlightGear or do sudo apt-get
install flightgear. Both will automatically install SimGear as well.

I've installed the version I uploaded and things seem to be running
well. I have encountered two problems so far. One is that I don't see
any AI aircraft, but I'm not sure if that's just me or if it's a bug.
Another is that some patches of terrain are dark, but as I get closer,
they turn light and can be seen again. I'm on an Intel GPU, so I'm not
sure if it's because of that.

Anyways, I've uploaded some screenshots from 2.10.0 here
https://picasaweb.google.com/103387392510447269112/FlightGear2100?authuser=0authkey=Gv1sRgCKXaocKSqp2G_wEfeat=directlink
(the black plane is, I'm assuming, a GPU bug since 2.8.0).

--
Saikrishna Arcot

--
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
is your hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials, tech docs,
whitepapers, evaluation guides, and opinion stories. Check out the most
recent posts - join the conversation now. http://goparallel.sourceforge.net/___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Simgear fix mingw - broke windows


On 18 Feb 2013, at 09:42, Frederic Bouvier fredfgf...@free.fr wrote:

 The commit “fix mingw” has broken native windows.
 
 3 sample_group.cxx
 3C:\FlightGear\simgear\simgear\sound\sample_group.cxx(37): error
 C2039: '_isnan' : is not a member of 'std'
 3C:\FlightGear\simgear\simgear\sound\sample_group.cxx(37): error
 C2873: '_isnan' : symbol cannot be used in a using-declaration
 
 BTW, there is a _isnan check in CMakeList.txt. See :
 https://gitorious.org/fg/simgear/blobs/next/CMakeLists.txt#line279

Okay - shall I back this out? I can't test either MSVC or mingw locally, I was 
hoping the changes were safe enough to apply, my mistake.

James


--
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Simgear fix mingw - broke windows

2013-02-18 Thread Frederic Bouvier

 De: James Turner zakal...@mac.com
 
 On 18 Feb 2013, at 09:42, Frederic Bouvier fredfgf...@free.fr
 wrote:
 
  The commit “fix mingw” has broken native windows.
  
  3 sample_group.cxx
  3C:\FlightGear\simgear\simgear\sound\sample_group.cxx(37): error
  C2039: '_isnan' : is not a member of 'std'
  3C:\FlightGear\simgear\simgear\sound\sample_group.cxx(37): error
  C2873: '_isnan' : symbol cannot be used in a using-declaration
  
  BTW, there is a _isnan check in CMakeList.txt. See :
  https://gitorious.org/fg/simgear/blobs/next/CMakeLists.txt#line279
 
 Okay - shall I back this out? I can't test either MSVC or mingw
 locally, I was hoping the changes were safe enough to apply, my
 mistake.

I am away from my computer currently. A safe change should be :

#ifdef HAVE_STD_ISNAN
using std::isnan;
#endif

instead of the single line added :
using std::isnan;

(to sample_group.cxx)

Regards,
-Fred


--
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Aircraft Checklists

2013-02-18 Thread Stuart Buchanan

On Sun, Feb 17, 2013 at 11:56 PM, Alan Teeder wrote:
 The reason for my query was that I have found making a representative set of
 checklists is becoming  very unwieldy.

 With just my entering the cockpit checks, I have already made 9 separate
 checklist.  Each one has about 10 checks. I have made one checklist per
 check list card on the real aircraft. These  checklist items disappear off
 the top of the menu list screen, and there is no indications as to which
 checklists/cards have been completed, or which is the next to do.

 Having got this far it is obvious that the current system will not cope for
 the rest of the aircraft checklists that I intend to replicate.

OK,  sounds like you've got much longer checklists than I have encountered
myself.

I'll see what I can do to support multi-page checklists.  I can probably add
Next and Previous buttons to page through the checklist.

One question:  Would you prefer that the UI itself split the checklist up,
or for the checklist author to do it themselves?  The former would be
automatic, but wouldn't allow the author to place the page-break where
they wished.

 Yes, my level of simulation will include such detail as the fail to relight
 in 20 seconds scenario.

Very good :)

 For background info my suggestions were based upon an interactive checklist
 system that I was involved with in the 1980´s as part of a joint BAC/Hawker
 Siddeley  glass cockpit simulation. This was before the two companies merged
 to form BAe.  AFAIK this was the first glass cockpit project to have an in
 depth simulator evaluation. Our two target aircraft were the VC10 (
 completely eliminating the flight engineer station) and the A300 which was
 state of the art at that time.

 This electronic checklist also bought up the relevant systems displays on
 one or more other front panel CRT´s . In normal use (e.g. start-up) the
 electronic checklist was selected by the crew, but the relevant set of
 checks were automatically initiated when aircraft failures were detected.
 The system was intelligent enough to follow the sequence of events following
 an emergency (e.g. my relight scenario) , and also had a priority system to
 deal with the major faults (engine failure, fire, etc)  before lesser ones.

 At the moment my TSR2 is not a glass cockpit, but having a usable checklist
 system would save a lot of paper.

 AS an old fogey I am not up to speed with current developments in this
 field, but am sure that some of our work has a modern counterpart.

Yup, and I think that would be the glass cockpit of the aircraft itself rather
than the simulator UI.

 Anyway - you asked for comments on your checklist system ;)

Yup, and very good feedback it is as well.  Thanks.

-Stuart

--
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] OSX 10.5 compilation

2013-02-18 Thread ys

Hi James

Have some news, I got sound back with simgear/sound/openal_tests, compiled 
against sdk 10.6. Now I'm going to make some other tests with fg vs. 10.5. What 
I changed in my chain is nuking macports boost 1.52 and bringing back 1.50 with 
a manual install on the slave.

I've seen that your jenkins slave uses 1.52. Maybe this works well with 
devtools = 4, here I'm using 3.2.6 for the slave to get sdk 10.5. Is there a 
reason to install boost 1.52, or is 1.50 ok for the next days ? ;-) And another 
question, do you remember what options you used for installing boost 1.52 on 
the slave ?

Thanks, Yves 



Am 18.02.2013 um 03:01 schrieb ys flightg...@sablonier.ch:

 
 
 
 
 
 Am 16.02.2013 um 00:56 schrieb ys flightg...@sablonier.ch:
 
 so I really have no idea what might be going.
 
 Hi James
 
 Me too. But it is still here. SimGear throws the same issue with all 
 combinations I tried, and now after goinf for 2.10 also with SDK 10.6. 
 Meantime I guess it is more a general problem, I don't know what the 
 wavreader throws when the path is wrong to the wav file i.e. Because in the 
 error message I don't see any path, and when I'm looking to the wavreader 
 code it should throw the path, or not ? So next question is does the 
 wavreader throw truncated or corrupt when it doesn't find the .wav file ? I 
 edited the simgear code and realised that what I see in fg log is the first 
 exception that can be thrown with message truncate/corrupt.
 
 Any other ideas what I should take into account ?
 
 -Yves
 --
 The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
 is your hub for all things parallel software development, from weekly thought 
 leadership blogs to news, videos, case studies, tutorials, tech docs, 
 whitepapers, evaluation guides, and opinion stories. Check out the most 
 recent posts - join the conversation now. http://goparallel.sourceforge.net/
 ___
 Flightgear-devel mailing list
 Flightgear-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/flightgear-devel

--
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Aircraft Checklists

2013-02-18 Thread Alan Teeder

Stuart.

Just came in from the garden and saw your reply.

In real life checklists get much, much more complicated when he aircraft has 
systems. A glider or a basic Cessna will be quite simple.

I would prefer that the author can add his own page breaks.  The checklist 
cards that I working on at the moment are organised in that manner. For 
example my Entering Cockpit checklist is split into 9 separate cards, 
which are meant to be used in a left to right order - starting with the rear 
left hand console panel, working forwards to the instrument panels and the 
rearwards along the right hand console. There is one card per panel. The 
take-off, engine start and other drills are similarly split into logical 
sections.

Yes, our simulator had visits from Boeing and other overseas companies. We 
displayed at Farnborough and on BBC TV. As you know, the VC10 was the last 
large aircraft that was a solely UK project. This simulator was built to a 
systems training simulator standard, which made it practically the same as a 
full simulator , but without visual or motion systems. I was given a  PDP 
11/45, practically fully expanded and costing about 100,000$, to host the 
FDM, autopilot and navigation. A second team had a PDP11/20 and a PDP 11/05 
to handle the systems (including checklists) and drive the CRT display 
hardware. Prices and computer power have changed since then.

Alan



-Original Message- 
From: Stuart Buchanan
Sent: Monday, February 18, 2013 1:26 PM
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Aircraft Checklists

On Sun, Feb 17, 2013 at 11:56 PM, Alan Teeder wrote:
 The reason for my query was that I have found making a representative set 
 of
 checklists is becoming  very unwieldy.

 With just my entering the cockpit checks, I have already made 9 separate
 checklist.  Each one has about 10 checks. I have made one checklist per
 check list card on the real aircraft. These  checklist items disappear off
 the top of the menu list screen, and there is no indications as to which
 checklists/cards have been completed, or which is the next to do.

 Having got this far it is obvious that the current system will not cope 
 for
 the rest of the aircraft checklists that I intend to replicate.

OK,  sounds like you've got much longer checklists than I have encountered
myself.

I'll see what I can do to support multi-page checklists.  I can probably add
Next and Previous buttons to page through the checklist.

One question:  Would you prefer that the UI itself split the checklist up,
or for the checklist author to do it themselves?  The former would be
automatic, but wouldn't allow the author to place the page-break where
they wished.

 Yes, my level of simulation will include such detail as the fail to 
 relight
 in 20 seconds scenario.

Very good :)

 For background info my suggestions were based upon an interactive 
 checklist
 system that I was involved with in the 1980´s as part of a joint 
 BAC/Hawker
 Siddeley  glass cockpit simulation. This was before the two companies 
 merged
 to form BAe.  AFAIK this was the first glass cockpit project to have an in
 depth simulator evaluation. Our two target aircraft were the VC10 (
 completely eliminating the flight engineer station) and the A300 which was
 state of the art at that time.

 This electronic checklist also bought up the relevant systems displays on
 one or more other front panel CRT´s . In normal use (e.g. start-up) the
 electronic checklist was selected by the crew, but the relevant set of
 checks were automatically initiated when aircraft failures were detected.
 The system was intelligent enough to follow the sequence of events 
 following
 an emergency (e.g. my relight scenario) , and also had a priority system 
 to
 deal with the major faults (engine failure, fire, etc)  before lesser 
 ones.

 At the moment my TSR2 is not a glass cockpit, but having a usable 
 checklist
 system would save a lot of paper.

 AS an old fogey I am not up to speed with current developments in this
 field, but am sure that some of our work has a modern counterpart.

Yup, and I think that would be the glass cockpit of the aircraft itself 
rather
than the simulator UI.

 Anyway - you asked for comments on your checklist system ;)

Yup, and very good feedback it is as well.  Thanks.

-Stuart

--
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
is your hub for all things parallel software development, from weekly 
thought
leadership blogs to news, videos, case studies, tutorials, tech docs,
whitepapers, evaluation guides, and opinion stories. Check out the most
recent posts - join the conversation now. http://goparallel.sourceforge.net/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Release 2.10.0: Decision Altitude

Hi Christian,

I completely blew away my build_flightgear and build_simgear
directories so they should be totally clean for the latest version of the
source code.  Are our cmake rules doing something they shouldn't and
writing files in the original source tree when you do out of source builds?

I thought (I was 100% sure until now that you say there was a problem) that
I looked at version.h in my build_simgear directory and it said 2.10.0

I really want to get this fixed as quickly as possible, but I'm confused as
to where things could be going wrong or how to fix it. Back in the day I
had the automake tools really figured out for myself at a deep level, but I
unfortunately don't have that same level of groking for the cmake tools.

Curt.


On Mon, Feb 18, 2013 at 4:31 AM, Christian Schmitt ch...@ilovelinux.dewrote:

 Curt,

 I noticed the SG/FG packages got updated on the mirrors. So I checked
 them out again: still the same issue. How did you create the source
 tarballs? Having the version number 2.8 in it looks like they were
 created from an older, used git clone and not a fresh or cleaned up
 one. The tarballs should only contain files that are in git, nothing
 that gets created during configure/compile time.

 Chris



 Curtis Olson wrote:

  Certainly this is my fault, however, I must misunderstand something
 about
  cmake for this to happen.  Can someone enlighten me and tell me what
 I
  need
  to do to fix this?  Maybe there is something we can tweak in the
 future if
  the default behavior requires manual intervention to achieve the
 correct
  outcome?
 
  Thanks for checking this out Chris.
 
  Curt.


 --
 The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
 is your hub for all things parallel software development, from weekly
 thought
 leadership blogs to news, videos, case studies, tutorials, tech docs,
 whitepapers, evaluation guides, and opinion stories. Check out the most
 recent posts - join the conversation now.
 http://goparallel.sourceforge.net/
 ___
 Flightgear-devel mailing list
 Flightgear-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/flightgear-devel




-- 
Curtis Olson:
http://www.atiak.com - http://aem.umn.edu/~uav/
http://www.flightgear.org - http://gallinazo.flightgear.org
--
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Release 2.10.0: Decision Altitude

Ok, I see now that in simgear-2.10.tar.bz2 the top level file version
does report 2.10.0 but the simgear/version.h file is saying 2.8.0

So my question are:

1. for an out-of-source build, why is the build system writing files in the
source tree?  Can we fix that?
2. what is the proper cmake fix here so it doesn't happen in the future?

Thanks,

Curt.



On Mon, Feb 18, 2013 at 8:26 AM, Curtis Olson curtol...@flightgear.orgwrote:

 Hi Christian,

 I completely blew away my build_flightgear and build_simgear
 directories so they should be totally clean for the latest version of the
 source code.  Are our cmake rules doing something they shouldn't and
 writing files in the original source tree when you do out of source builds?

 I thought (I was 100% sure until now that you say there was a problem)
 that I looked at version.h in my build_simgear directory and it said
 2.10.0

 I really want to get this fixed as quickly as possible, but I'm confused
 as to where things could be going wrong or how to fix it. Back in the day I
 had the automake tools really figured out for myself at a deep level, but I
 unfortunately don't have that same level of groking for the cmake tools.

 Curt.


 On Mon, Feb 18, 2013 at 4:31 AM, Christian Schmitt ch...@ilovelinux.dewrote:

 Curt,

 I noticed the SG/FG packages got updated on the mirrors. So I checked
 them out again: still the same issue. How did you create the source
 tarballs? Having the version number 2.8 in it looks like they were
 created from an older, used git clone and not a fresh or cleaned up
 one. The tarballs should only contain files that are in git, nothing
 that gets created during configure/compile time.

 Chris



 Curtis Olson wrote:

  Certainly this is my fault, however, I must misunderstand something
 about
  cmake for this to happen.  Can someone enlighten me and tell me what
 I
  need
  to do to fix this?  Maybe there is something we can tweak in the
 future if
  the default behavior requires manual intervention to achieve the
 correct
  outcome?
 
  Thanks for checking this out Chris.
 
  Curt.


 --
 The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
 is your hub for all things parallel software development, from weekly
 thought
 leadership blogs to news, videos, case studies, tutorials, tech docs,
 whitepapers, evaluation guides, and opinion stories. Check out the most
 recent posts - join the conversation now.
 http://goparallel.sourceforge.net/
 ___
 Flightgear-devel mailing list
 Flightgear-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/flightgear-devel




 --
 Curtis Olson:
 http://www.atiak.com - http://aem.umn.edu/~uav/
 http://www.flightgear.org - http://gallinazo.flightgear.org




-- 
Curtis Olson:
http://www.atiak.com - http://aem.umn.edu/~uav/
http://www.flightgear.org - http://gallinazo.flightgear.org
--
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] 2.10 tarball problem

We are currently looking into this, sorry for the glitch.  It sounds like
you have a simple work around for now and we'll be trying to update the
official tar balls as soon as we can iron our out this problem on our end.

Thanks,

Curt.


On Mon, Feb 18, 2013 at 4:57 AM, zezinho lists.jjo...@free.fr wrote:

 hi, I am the package maintainer of flightgear for Mageia distribution.

 In IRC, the hint was told me about version.h removal to use 2.10 data...
 maybe this info should go to download page, or tarballs be redone?

 thanks


 --
 The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
 is your hub for all things parallel software development, from weekly
 thought
 leadership blogs to news, videos, case studies, tutorials, tech docs,
 whitepapers, evaluation guides, and opinion stories. Check out the most
 recent posts - join the conversation now.
 http://goparallel.sourceforge.net/
 ___
 Flightgear-devel mailing list
 Flightgear-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/flightgear-devel




-- 
Curtis Olson:
http://www.atiak.com - http://aem.umn.edu/~uav/
http://www.flightgear.org - http://gallinazo.flightgear.org
--
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Release 2.10.0: Decision Altitude

On 02/18/2013 03:36 PM, Curtis Olson wrote:
 Ok, I see now that in simgear-2.10.tar.bz2 the top level file version
 does report 2.10.0 but the simgear/version.h file is saying 2.8.0

 So my question are:

 1. for an out-of-source build, why is the build system writing files in
 the source tree?  Can we fix that?
 2. what is the proper cmake fix here so it doesn't happen in the future?

I see that simgear/CMakeList.txt defines:

file(WRITE ${PROJECT_BINARY_DIR}/simgear/version.h #define 
SIMGEAR_VERSION ${SIMGEAR_VERSION})

it would be better to create a version.h.in file and use

CONFIGURE_FILE(
 ${CMAKE_CURRENT_SOURCE_DIR}/simgear/version.h.in

containing:
#define SIMGEAR_VERSION   @SIMGEAR_VERSION@

Erik

-- 
http://www.adalin.com
- Hardware accelerated AeonWave and OpenAL for Windows and Linux

--
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Release 2.10.0: Decision Altitude


On 18 Feb 2013, at 14:57, Erik Hofman e...@ehofman.com wrote:

 
 I see that simgear/CMakeList.txt defines:
 
 file(WRITE ${PROJECT_BINARY_DIR}/simgear/version.h #define 
 SIMGEAR_VERSION ${SIMGEAR_VERSION})
 
 it would be better to create a version.h.in file and use
 
 CONFIGURE_FILE(
 ${CMAKE_CURRENT_SOURCE_DIR}/simgear/version.h.in
 
 containing:
 #define SIMGEAR_VERSION   @SIMGEAR_VERSION@

Hmm, I don't think it matter *how* you write the file: PROJECT_BINARY_DIR seems 
like the correct place based on my understand of cmake. I could be wrong of 
course, but it makes more sense to me than CMAKE_CURRENT_SOURCE_DIR.

Since, we want to write version.h inside the build tree - the install hierarchy 
is no use, and we certainly don't want to write to the source dir!

James


--
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Release 2.10.0: Decision Altitude



Ok that got tangled up. Here's a diff.

Erik

--
http://www.adalin.com
- Hardware accelerated AeonWave and OpenAL for Windows and Linux
diff --git a/simgear/CMakeLists.txt b/simgear/CMakeLists.txt
index b4e299a..0725a78 100644
--- a/simgear/CMakeLists.txt
+++ b/simgear/CMakeLists.txt
@@ -1,5 +1,7 @@
 
-file(WRITE ${PROJECT_BINARY_DIR}/simgear/version.h #define SIMGEAR_VERSION ${SIMGEAR_VERSION})
+CONFIGURE_FILE(
+ ${CMAKE_CURRENT_SOURCE_DIR}/version.h.in
+ ${CMAKE_CURRENT_BINARY_DIR}/version.h)
 
 foreach( mylibfolder 
 bucket
diff --git a/simgear/version.h.in b/simgear/version.h.in
index 635495e..a3def5d 100644
--- a/simgear/version.h.in
+++ b/simgear/version.h.in
@@ -26,7 +26,7 @@
 #define _SIMGEAR_VERSION_H
 
 
-#define SIMGEAR_VERSION @VERSION@
+#define SIMGEAR_VERSION @SIMGEAR_VERSION@
 
 
 #endif // _SIMGEAR_VERSION_H
--
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Release 2.10.0: Decision Altitude

On 02/18/2013 04:04 PM, James Turner wrote:
 Hmm, I don't think it matter *how* you write the file: PROJECT_BINARY_DIR 
 seems like the correct place based on my understand of cmake. I could be 
 wrong of course, but it makes more sense to me than CMAKE_CURRENT_SOURCE_DIR.

You seem to be correct, when doing a make package_source I see
simgear-2.11.0/build/simgear/version.h

More investigation to do

Erik
-- 
http://www.adalin.com
- Hardware accelerated AeonWave and OpenAL for Windows and Linux

--
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Release 2.10.0: Decision Altitude

On 02/18/2013 04:08 PM, Erik Hofman wrote:
 On 02/18/2013 04:04 PM, James Turner wrote:
 Hmm, I don't think it matter *how* you write the file: PROJECT_BINARY_DIR 
 seems like the correct place based on my understand of cmake. I could be 
 wrong of course, but it makes more sense to me than CMAKE_CURRENT_SOURCE_DIR.

 You seem to be correct, when doing a make package_source I see
 simgear-2.11.0/build/simgear/version.h

 More investigation to do

I suspect:

set(HEADERS compiler.h constants.h sg_inlines.h 
${PROJECT_BINARY_DIR}/simgear/version.h)

is the culprit.

Erik

-- 
http://www.adalin.com
- Hardware accelerated AeonWave and OpenAL for Windows and Linux

--
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Release 2.10.0: Decision Altitude

2013-02-18 Thread Christian Schmitt

Sorry Curt,

but nothing writes into the source dir if you use a sane, clean and 
proper checkout from git. Your tarballs make me think that you already 
ran cmake inside the source dir prior to packaging them. Could you run 
git clean -fdx inside the source dir and tar the result up again? 
This will eliminate any remains from prior cmake processings.

Chris


Curtis Olson wrote:

 Ok, I see now that in simgear-2.10.tar.bz2 the top level file 
version
 does report 2.10.0 but the simgear/version.h file is saying 2.8.0
 
 So my question are:
 
 1. for an out-of-source build, why is the build system writing files 
in
 the
 source tree?  Can we fix that?
 2. what is the proper cmake fix here so it doesn't happen in the 
future?
 

--
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Release 2.10.0: Decision Altitude


On 18 Feb 2013, at 15:10, Erik Hofman e...@ehofman.com wrote:

 You seem to be correct, when doing a make package_source I see
 simgear-2.11.0/build/simgear/version.h

The tar balls created by Jenkins (Linux-release) seem to be fine. They contain 
version.h.in, but no version.h

They're created by the following script:

https://gitorious.org/fg/fgmeta/blobs/master/hudson_build_release.sh

And the results look 100% correct to me (download and check for yourselves: 
http://flightgear.simpits.org:8080/job/Linux-release/ )

James


--
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Release 2.10.0: Decision Altitude

Maybe something has already been tweaked between v2.8 and v2.10.  After I
manually removed the simgear/version.h file it did not come back again --
so maybe we will be in good shape for future releases.

I noticed that simgear/version.h (along with all the other build time
files) are explicitely listed in the .gitignore files throughout simgear.

Here is me wondering out loud: If we *strongly* recommend out of source
builds, maybe it would make sense to *not* list build files in the
.gitignore so they clearly show up as an anomoly.  Previously when I did a
git status, it showed a pristine git tree on the 2.10 branch with no
changes or differences -- but the problem was hidden because of the
.gitignore file.

I found the git status --ignored command which shows ignored files, but
this is a lot of manual messing around to have to remember every 6 months
-- especially when 6 months is about the shelf life of remember specific
details on how or what I've done in the past if haven't repeated it since.
:-)

Anway, I have updated the source files on the ftp server and hopefully we
are ok for this release now.

Curt.


On Mon, Feb 18, 2013 at 9:10 AM, Erik Hofman e...@ehofman.com wrote:

 On 02/18/2013 04:08 PM, Erik Hofman wrote:
  On 02/18/2013 04:04 PM, James Turner wrote:
  Hmm, I don't think it matter *how* you write the file:
 PROJECT_BINARY_DIR seems like the correct place based on my understand of
 cmake. I could be wrong of course, but it makes more sense to me than
 CMAKE_CURRENT_SOURCE_DIR.
 
  You seem to be correct, when doing a make package_source I see
  simgear-2.11.0/build/simgear/version.h
 
  More investigation to do

 I suspect:

 set(HEADERS compiler.h constants.h sg_inlines.h
 ${PROJECT_BINARY_DIR}/simgear/version.h)

 is the culprit.

 Erik

 --
 http://www.adalin.com
 - Hardware accelerated AeonWave and OpenAL for Windows and Linux


 --
 The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
 is your hub for all things parallel software development, from weekly
 thought
 leadership blogs to news, videos, case studies, tutorials, tech docs,
 whitepapers, evaluation guides, and opinion stories. Check out the most
 recent posts - join the conversation now.
 http://goparallel.sourceforge.net/
 ___
 Flightgear-devel mailing list
 Flightgear-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/flightgear-devel




-- 
Curtis Olson:
http://www.atiak.com - http://aem.umn.edu/~uav/
http://www.flightgear.org - http://gallinazo.flightgear.org
--
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Release 2.10.0: Decision Altitude



The 'make package_source' problem was related to this diff.

Erik

--
http://www.adalin.com
- Hardware accelerated AeonWave and OpenAL for Windows and Linux
diff --git a/CMakeLists.txt b/CMakeLists.txt
index f6dd5fe..615b82e 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -42,7 +42,7 @@ if (NOT EMBEDDED_SIMGEAR)
 set(CPACK_SOURCE_GENERATOR TBZ2)
 set(CPACK_SOURCE_PACKAGE_FILE_NAME simgear-${SIMGEAR_VERSION} CACHE INTERNAL tarball basename)
 set(CPACK_SOURCE_IGNORE_FILES
-  ^${PROJECT_SOURCE_DIR}/.git;.gitignore;Makefile.am;~$;${CPACK_SOURCE_IGNORE_FILES})
+  ^${PROJECT_SOURCE_DIR}/.git;.gitignore;Makefile.am;~$;${CMAKE_CURRENT_BINARY_DIR}/simgear/version.h;${CPACK_SOURCE_IGNORE_FILES})
 
 message(STATUS ignoring: ${CPACK_SOURCE_IGNORE_FILES})
 
--
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Manual update request (Was: Updated Short Reference for 2.10.0)

2013-02-18 Thread YOSHIMATSU Toshihide

Hi Olivier,

I saw your latest commit of
http://gitorious.org/fg/getstart/commit/2c00caf3d7f00d69e02b0c6f3ed0c1903763e3d1

And now I noticed that I had written wrong link in my previous post.
That was my fault.
I'm sorry for the complication.

Simply saying, https://dealer.bendixking.com/... is OK.
But https://www3.bendixking.com/... is NG.

Below is my new suggestion to correct the link.
However, as I don't have TeX environments on my machine, I'm not sure if 
it can work as intended...

* New suggestion to basic.tex, line 1859:
\weblong{https://dealer.bendixking.com/servlet/com.honeywell.aes.utility.PDFDownLoadServlet?FileName=/TechPubs/repository/006-18034-_3.pdf}{https://dealer.bendixking.com/servlet/com.honeywell.aes.utility\\.PDFDownLoadServlet?FileName=/TechPubs/repository\\/006-18034-\_3.pdf}

Cheers,
Toshi


--
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] OSX 10.5 compilation

2013-02-18 Thread ys

O, happy now.

Finally it is working. And 2.10 is really a hit, compiled against sdk 10.5. One 
can still use an older macbook for simple multi-machine fun, with an old osx 
with bad bad graphics (old ATI, almost no vram). Now turning on 3d clouds, 
water, crop and transistion shader ... everything looks fine with a reasonable 
framerate (around 20fps). Only atmospheric lights, urban shader, random 
buildings/vegetation and some AI traffic reduces framerate to a no go. But 
really, well done, thanks guys. And special thanks to James and others nuking 
alut and making building sg/fg on a mac easier and easier (beside of my sound 
and boost troubles the last days, but that's just a private 2.10/osx learning 
curve here, I see).

I am happy for the rest of the week (and shut up) because I got 2.10 working 
now from OSX 10.5 to 8, with simply downgrading boost and nuking macports. I 
will publish a version with FGx asap.

Now I see that the small cocoa change for flightgear making compiling possible 
for 10.5 has already been merged by James, thanks, the patch for the simgear 
sdk 10.5 svn problem will follow asap.

Thanks, Yves




Am 18.02.2013 um 14:41 schrieb ys flightg...@sablonier.ch:

 Hi James
 
 Have some news, I got sound back with simgear/sound/openal_tests, compiled 
 against sdk 10.6. Now I'm going to make some other tests with fg vs. 10.5. 
 What I changed in my chain is nuking macports boost 1.52 and bringing back 
 1.50 with a manual install on the slave.
 
 I've seen that your jenkins slave uses 1.52. Maybe this works well with 
 devtools = 4, here I'm using 3.2.6 for the slave to get sdk 10.5. Is there a 
 reason to install boost 1.52, or is 1.50 ok for the next days ? ;-) And 
 another question, do you remember what options you used for installing boost 
 1.52 on the slave ?
 
 Thanks, Yves 
 
 
 
 Am 18.02.2013 um 03:01 schrieb ys flightg...@sablonier.ch:
 
 
 
 
 
 
 Am 16.02.2013 um 00:56 schrieb ys flightg...@sablonier.ch:
 
 so I really have no idea what might be going.
 
 Hi James
 
 Me too. But it is still here. SimGear throws the same issue with all 
 combinations I tried, and now after goinf for 2.10 also with SDK 10.6. 
 Meantime I guess it is more a general problem, I don't know what the 
 wavreader throws when the path is wrong to the wav file i.e. Because in the 
 error message I don't see any path, and when I'm looking to the wavreader 
 code it should throw the path, or not ? So next question is does the 
 wavreader throw truncated or corrupt when it doesn't find the .wav file ? 
 I edited the simgear code and realised that what I see in fg log is the 
 first exception that can be thrown with message truncate/corrupt.
 
 Any other ideas what I should take into account ?
 
 -Yves
 --
 The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
 is your hub for all things parallel software development, from weekly 
 thought 
 leadership blogs to news, videos, case studies, tutorials, tech docs, 
 whitepapers, evaluation guides, and opinion stories. Check out the most 
 recent posts - join the conversation now. http://goparallel.sourceforge.net/
 ___
 Flightgear-devel mailing list
 Flightgear-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/flightgear-devel
 
 --
 The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
 is your hub for all things parallel software development, from weekly thought 
 leadership blogs to news, videos, case studies, tutorials, tech docs, 
 whitepapers, evaluation guides, and opinion stories. Check out the most 
 recent posts - join the conversation now. http://goparallel.sourceforge.net/
 ___
 Flightgear-devel mailing list
 Flightgear-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/flightgear-devel

--
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] OSX 10.5 compilation

On Mon, Feb 18, 2013 at 11:00 AM, ys wrote:

 O, happy now.

 Finally it is working. And 2.10 is really a hit, compiled against sdk
 10.5. One can still use an older macbook for simple multi-machine fun, with
 an old osx with bad bad graphics (old ATI, almost no vram). Now turning on
 3d clouds, water, crop and transistion shader ... everything looks fine
 with a reasonable framerate (around 20fps). Only atmospheric lights, urban
 shader, random buildings/vegetation and some AI traffic reduces framerate
 to a no go. But really, well done, thanks guys. And special thanks to James
 and others nuking alut and making building sg/fg on a mac easier and easier
 (beside of my sound and boost troubles the last days, but that's just a
 private 2.10/osx learning curve here, I see).

 I am happy for the rest of the week (and shut up) because I got 2.10
 working now from OSX 10.5 to 8, with simply downgrading boost and nuking
 macports. I will publish a version with FGx asap.

 Now I see that the small cocoa change for flightgear making compiling
 possible for 10.5 has already been merged by James, thanks, the patch for
 the simgear sdk 10.5 svn problem will follow asap.


I haven't been following this thread too closely, but is it possible to get
10.5 support back into the official build on Jenkins or does it require a
separate build/installer for 10.5 support?

Thanks,

Curt.
-- 
Curtis Olson:
http://www.atiak.com - http://aem.umn.edu/~uav/
http://www.flightgear.org - http://gallinazo.flightgear.org
--
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Simgear fix mingw - broke windows

2013-02-18 Thread Alan Teeder

I have a clean build and run on MSVC10 now.

Thanks

Alan

--
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

[Flightgear-devel] Website update request

2013-02-18 Thread YOSHIMATSU Toshihide

Hi Curt,

Nice to see your v2.10 release anouncement on the website!

Today, I found one link error.

* http://www.flightgear.org/download/
- Download v2.10 Aircraft links to
  http://www.flightgear.org/download/aircraft-v2-10-filterable
  which does not exist.
  Correct link should be
  http://www.flightgear.org/download/aircraft-2-10-filterable/
  (delete v).

And I'm happy if I can hear your comments for my question below (I
edited typos).

(2013/02/13 7:48), YOSHIMATSU Toshihide wrote:
 Chapter 1.3 Further Reading includes the link to
 http://www.flightgear.org/Docs/FGShortRef.pdf

 However, FGShortRef.pdf on www.flightgear.org is outdated (v2.0.0).

 Can Curt update FGShortRef.pdf before 2.10.0 and future release?

 Or do we consider to prepare automatically generated FGShortRef.pdf and
 FGShortRef.html on mapserver.flightgear.org?

Cheers,
Toshi

--
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Website update request

2013-02-18 Thread Gijs de Rooy


 Today, I found one link error.
 
 * http://www.flightgear.org/download/

And on that same page, 2.8.0 release candidates can probably go ;-)

Cheers,
Gijs
  --
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] OSX 10.5 compilation


On 18 Feb 2013, at 17:08, Curtis Olson curtol...@flightgear.org wrote:

 I haven't been following this thread too closely, but is it possible to get 
 10.5 support back into the official build on Jenkins or does it require a 
 separate build/installer for 10.5 support?
 

I think the answer is no, since the build slave runs 10.6.

If someone else disagrees, then I need to proceed carefully, since rebuilding 
the slave if we screw something up is not fun. (I could image the drive, I 
guess)

James
--
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Website update request

Hi Toshi,

Thanks for catching the broken link.  It should now be fixed.  There's
always a zillion things to update with each new release and once in a while
something falls through the cracks.

Gijs, I triaged the comments about 2.8.0 release candidates.

Curt.


On Mon, Feb 18, 2013 at 11:35 AM, Gijs de Rooy gijsr...@hotmail.com wrote:


  Today, I found one link error.
 
  * http://www.flightgear.org/download/

 And on that same page, 2.8.0 release candidates can probably go ;-)

 Cheers,
 Gijs


 --
 The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
 is your hub for all things parallel software development, from weekly
 thought
 leadership blogs to news, videos, case studies, tutorials, tech docs,
 whitepapers, evaluation guides, and opinion stories. Check out the most
 recent posts - join the conversation now.
 http://goparallel.sourceforge.net/
 ___
 Flightgear-devel mailing list
 Flightgear-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/flightgear-devel




-- 
Curtis Olson:
http://www.atiak.com - http://aem.umn.edu/~uav/
http://www.flightgear.org - http://gallinazo.flightgear.org
--
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

[Flightgear-devel] Flightgear GIT

2013-02-18 Thread Wil Neeley

How to I download the newest experimental versions of flightgear
Wil Neeley
--
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Flightgear GIT

You can get the flightgear and simgear gits at 
https://gitorious.org/fg. I think the next branch is the development 
branch.

Saikrishna Arcot

On Mon 18 Feb 2013 06:37:04 PM CST, Wil Neeley wrote:
 How to I download the newest experimental versions of flightgear
 Wil Neeley


 --
 The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
 is your hub for all things parallel software development, from weekly thought
 leadership blogs to news, videos, case studies, tutorials, tech docs,
 whitepapers, evaluation guides, and opinion stories. Check out the most
 recent posts - join the conversation now. http://goparallel.sourceforge.net/


 ___
 Flightgear-devel mailing list
 Flightgear-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/flightgear-devel

--
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Flightgear GIT

2013-02-18 Thread Wil Neeley

Thanks

Wil Neeley


On Mon, Feb 18, 2013 at 8:04 PM, Saikrishna Arcot saiarcot...@gmail.comwrote:

 You can get the flightgear and simgear gits at
 https://gitorious.org/fg. I think the next branch is the development
 branch.

 Saikrishna Arcot

 On Mon 18 Feb 2013 06:37:04 PM CST, Wil Neeley wrote:
  How to I download the newest experimental versions of flightgear
  Wil Neeley
 
 
 
 --
  The Go Parallel Website, sponsored by Intel - in partnership with
 Geeknet,
  is your hub for all things parallel software development, from weekly
 thought
  leadership blogs to news, videos, case studies, tutorials, tech docs,
  whitepapers, evaluation guides, and opinion stories. Check out the most
  recent posts - join the conversation now.
 http://goparallel.sourceforge.net/
 
 
  ___
  Flightgear-devel mailing list
  Flightgear-devel@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/flightgear-devel


 --
 The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
 is your hub for all things parallel software development, from weekly
 thought
 leadership blogs to news, videos, case studies, tutorials, tech docs,
 whitepapers, evaluation guides, and opinion stories. Check out the most
 recent posts - join the conversation now.
 http://goparallel.sourceforge.net/
 ___
 Flightgear-devel mailing list
 Flightgear-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/flightgear-devel

--
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] OSX 10.5 compilation

2013-02-18 Thread ys

Hi Curt

I would not recommend to get 10.5 support back with current official jenkins 
build. AFAIK current mac build for 10.6/7/8 works very well, supporting 10.5 
would need heavy changes, or better, downgrading of slaves, and it is 
definitely not worth to break things this way. I'm free to do such on a small 
private CI, and I made a lot of noise about having 10.5 support back, but at 
the end it's just weird and for a very small minority of fg users like me. But 
it is documented, and everyone joining the adventure can do so ;-)

-Yves 




Am 18.02.2013 um 18:54 schrieb James Turner zakal...@mac.com:

 
 On 18 Feb 2013, at 17:08, Curtis Olson curtol...@flightgear.org wrote:
 
 I haven't been following this thread too closely, but is it possible to get 
 10.5 support back into the official build on Jenkins or does it require a 
 separate build/installer for 10.5 support?
 
 
 I think the answer is no, since the build slave runs 10.6.
 
 If someone else disagrees, then I need to proceed carefully, since rebuilding 
 the slave if we screw something up is not fun. (I could image the drive, I 
 guess)
 
 James
 --
 The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
 is your hub for all things parallel software development, from weekly thought 
 leadership blogs to news, videos, case studies, tutorials, tech docs, 
 whitepapers, evaluation guides, and opinion stories. Check out the most 
 recent posts - join the conversation now. http://goparallel.sourceforge.net/
 ___
 Flightgear-devel mailing list
 Flightgear-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/flightgear-devel

--
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Flightgear GIT

2013-02-18 Thread Wil Neeley

I am following the instructions on the flightgear wiki but when I run this
command

git pull -- depth 1 git://gitorious.org/fg/fgdata master

I get this error

fatal: Invalid refspec 'git://gitorious.org/fg/fgdata'

what am I doing wrong



Wil Neeley


On Mon, Feb 18, 2013 at 8:06 PM, Wil Neeley bentchic...@gmail.com wrote:

 Thanks

 Wil Neeley


 On Mon, Feb 18, 2013 at 8:04 PM, Saikrishna Arcot 
 saiarcot...@gmail.comwrote:

 You can get the flightgear and simgear gits at
 https://gitorious.org/fg. I think the next branch is the development
 branch.

 Saikrishna Arcot

 On Mon 18 Feb 2013 06:37:04 PM CST, Wil Neeley wrote:
  How to I download the newest experimental versions of flightgear
  Wil Neeley
 
 
 
 --
  The Go Parallel Website, sponsored by Intel - in partnership with
 Geeknet,
  is your hub for all things parallel software development, from weekly
 thought
  leadership blogs to news, videos, case studies, tutorials, tech docs,
  whitepapers, evaluation guides, and opinion stories. Check out the most
  recent posts - join the conversation now.
 http://goparallel.sourceforge.net/
 
 
  ___
  Flightgear-devel mailing list
  Flightgear-devel@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/flightgear-devel


 --
 The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
 is your hub for all things parallel software development, from weekly
 thought
 leadership blogs to news, videos, case studies, tutorials, tech docs,
 whitepapers, evaluation guides, and opinion stories. Check out the most
 recent posts - join the conversation now.
 http://goparallel.sourceforge.net/
 ___
 Flightgear-devel mailing list
 Flightgear-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/flightgear-devel



--
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Flightgear GIT

You're missing the .git part at the end.

Also, keep in mind that that will get the master branch, which seems to 
be currently at 2.10.0.

Saikrishna Arcot

On Mon 18 Feb 2013 07:14:31 PM CST, Wil Neeley wrote:
 I am following the instructions on the flightgear wiki but when I run
 this command
 git pull -- depth 1 git://gitorious.org/fg/fgdata master



 I get this error
 fatal: Invalid refspec 'git://gitorious.org/fg/fgdata 
 http://gitorious.org/fg/fgdata'

 what am I doing wrong


 Wil Neeley


 On Mon, Feb 18, 2013 at 8:06 PM, Wil Neeley bentchic...@gmail.com
 mailto:bentchic...@gmail.com wrote:

 Thanks

 Wil Neeley


 On Mon, Feb 18, 2013 at 8:04 PM, Saikrishna Arcot
 saiarcot...@gmail.com mailto:saiarcot...@gmail.com wrote:

 You can get the flightgear and simgear gits at
 https://gitorious.org/fg. I think the next branch is the
 development
 branch.

 Saikrishna Arcot

 On Mon 18 Feb 2013 06:37:04 PM CST, Wil Neeley wrote:
  How to I download the newest experimental versions of flightgear
  Wil Neeley
 
 
 
 
 --
  The Go Parallel Website, sponsored by Intel - in partnership
 with Geeknet,
  is your hub for all things parallel software development,
 from weekly thought
  leadership blogs to news, videos, case studies, tutorials,
 tech docs,
  whitepapers, evaluation guides, and opinion stories. Check
 out the most
  recent posts - join the conversation now.
 http://goparallel.sourceforge.net/
 
 
  ___
  Flightgear-devel mailing list
  Flightgear-devel@lists.sourceforge.net
 mailto:Flightgear-devel@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/flightgear-devel

 
 --
 The Go Parallel Website, sponsored by Intel - in partnership
 with Geeknet,
 is your hub for all things parallel software development, from
 weekly thought
 leadership blogs to news, videos, case studies, tutorials,
 tech docs,
 whitepapers, evaluation guides, and opinion stories. Check out
 the most
 recent posts - join the conversation now.
 http://goparallel.sourceforge.net/
 ___
 Flightgear-devel mailing list
 Flightgear-devel@lists.sourceforge.net
 mailto:Flightgear-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/flightgear-devel





 --
 The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
 is your hub for all things parallel software development, from weekly thought
 leadership blogs to news, videos, case studies, tutorials, tech docs,
 whitepapers, evaluation guides, and opinion stories. Check out the most
 recent posts - join the conversation now. http://goparallel.sourceforge.net/


 ___
 Flightgear-devel mailing list
 Flightgear-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/flightgear-devel

--
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Flightgear GIT