Just a heads up with MSVC10
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' :
De: Alan Teeder ajtee...@v-twin.org.uk
Just a heads up with MSVC10
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'
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
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
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
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'
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'
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
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
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
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
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
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
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?
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(
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
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,
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
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
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
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
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
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
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 ...
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
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
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
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
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
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,
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
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
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
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
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
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
PS: You need to remove the space between -- and depth.
Saikrishna Arcot
On Mon 18 Feb 2013 07:18:16 PM CST, Saikrishna Arcot wrote:
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
37 matches
Mail list logo
