It's now getting on for a week since the build on Simgear was broken for Win
64/MSVC by this mistake. Any chance of a fix sometime soon?
Vivian
From: James Turner [mailto:zakal...@mac.com]
Sent: 03 October 2013 22:53
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel
On 9 Oct 2013, at 10:23, Vivian Meazza vivian.mea...@lineone.net wrote:
It’s now getting on for a week since the build on Simgear was broken for Win
64/MSVC by this mistake. Any chance of a fix sometime soon?
Yes, was just about to push one - however you can always push such a fix
yourself!
* b.num;
return VALIDATE(a);
}
Alan
From: James Turner
Sent: Wednesday, October 09, 2013 10:51 AM
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Simgear ,mathlib.c line 1 65
On 9 Oct 2013, at 10:23, Vivian Meazza vivian.mea...@lineone.net wrote:
It’s now
On 9 Oct 2013, at 12:05, Alan Teeder ajtee...@v-twin.org.uk wrote:
Sorry, but the patch failed. It also needs the change suggested by Gijs, with
“double x,y;”
e.g.
Ah, I really hate C89 :)
Fix coming up.
James--
On Wed October 9 2013 12:23:56 James Turner wrote:
On 9 Oct 2013, at 12:05, Alan Teeder ajtee...@v-twin.org.uk wrote:
Sorry, but the patch failed. It also needs the change suggested by Gijs,
with “double x,y;” e.g.
Ah, I really hate C89 :)
Fix coming up.
Two same. Why not compile in cxx
James
Seems all OK now.
Thanks
Alan
P.S. MSVC has no compilation problems with the other commits you made today
wlEmoticon-winkingsmile[1].png
Description: Binary data
--
October Webinars: Code for Performance
Free
Also, double x; needs to be declared at the top of the function (and then you
will have x = round(a.num / b.num); of course).
Cheers,
Gijs
--
October Webinars: Code for
Re commit ad83e70cf5983c7b307847aa2cb92c40e42bc534
Author: James Turner
Date: Thu Oct 3 17:40:17 2013 +0100
Extend built-in Nasal math.
James
Sorry, but MSVC does not have a round function. ;(
Alan
--
On 3 Oct 2013, at 22:20, Alan Teeder ajtee...@v-twin.org.uk wrote:
Sorry, but MSVC does not have a round function. ;(
Yes, C99 is a cutting-edge spec :)
I'll add a replacement for MSVC, thanks for spotting my mistake.
Kind regards,
James
Can I make a suggestion..
What I want to do is create a simg...@freeflightsim.org as an user.
The idea is to knock out the latest bleeding edge docs and changes to
simgear..
Example is here..
http://docs.freeflightsim.org/simgear/
But I prefer a sub domain..
On the server,
Doxygen is installed
On 31 Jul 2013, at 01:16, Patrick Callahan pat.callah...@gmail.com wrote:
Check this out:
http://lists.openscenegraph.org/pipermail/osg-users-openscenegraph.org/2013-June/063519.html
I believe we've dealt with this issue - at least, I have tweaked Jenkins to
build the 3.2.0 release
OpenSceneGraph (3.2.0~rc1) was just uploaded and may be approved soon.
Check this out:
http://lists.openscenegraph.org/pipermail/osg-users-openscenegraph.org/2013-June/063519.html
comments?
On Tue, Jun 25, 2013 at 11:53 AM, Torsten Dreyer tors...@t3r.de wrote:
Hi,
I'm failing to build
Hello,
Back to that topic, referring to OSG 3.1.9
May be we must take in account these mailing:
https://groups.google.com/forum/#!topic/osg-users/UixZUSwpW7g
https://groups.google.com/forum/#!topic/osg-users/lOmJZtOCyAk
There, we can understand that coming osg stable 3.2 will follow the
2013/6/29 Clement de l'Hamaide clem...@hotmail.fr:
Today OSG has moved to 3.1.9 introducing a new bug :/
I can see the same - at least the last one - and was not able to find
a quick fix or problem report. For now I will stay with OSG 3.1.8 and
wait for a later development release or the 3.2
Hi all,
Today OSG has moved to 3.1.9 introducing a new bug :/
http://clemaez.fr/flightgear/Screenshot/Capture%20du%202013-06-29%2021:52:21.png
http://clemaez.fr/flightgear/Screenshot/Capture%20du%202013-06-29%2023:27:23.png
Am 27.06.2013 09:58, schrieb James Turner:
On 26 Jun 2013, at 23:05, Thomas Geymayer tom...@gmail.com
mailto:tom...@gmail.com wrote:
Thank you Alex! I've just commited your patch.
Yes thank indeed Alex, it's a relief to know someone is keeping
bleeding-edge OSG working, since the rate of
On 26 Jun 2013, at 23:05, Thomas Geymayer tom...@gmail.com wrote:
Thank you Alex! I've just commited your patch.
Yes thank indeed Alex, it's a relief to know someone is keeping bleeding-edge
OSG working, since the rate of change over there seems to be increasing (for
the better)
Torsten Dreyer tors...@t3r.de writes:
I'm failing to build SimGear on 64bit linux:
EffectGeode.cxx:83:136: error: no matching function for call to
‘osg::Geometry::setVertexAttribArray(int, osg::Geometry::ArrayData)’
OSG is stable 3.0.1 from svn (same with OSG trunk)
SimGear is git next
Am 2013-06-26 22:43, schrieb Alex Romosan:
these are the changes i made to get simgear to compile with
openscenegraph from svn:
Thank you Alex! I've just commited your patch.
Tom
--
This SF.net email is sponsored by
Hi,
I'm failing to build SimGear on 64bit linux:
EffectGeode.cxx:83:136: error: no matching function for call to
‘osg::Geometry::setVertexAttribArray(int, osg::Geometry::ArrayData)’
OSG is stable 3.0.1 from svn (same with OSG trunk)
SimGear is git next from today
Yes, I rm-rf'ed previous
Hi Torsten,
2013/6/25 Torsten Dreyer tors...@t3r.de:
I'm failing to build SimGear on 64bit linux:
EffectGeode.cxx:83:136: error: no matching function for call to
‘osg::Geometry::setVertexAttribArray(int, osg::Geometry::ArrayData)’
OSG is stable 3.0.1 from svn (same with OSG trunk)
SimGear
hello,
Linking CXX static library libSimGearCore.a
[ 46%] Built target SimGearCore
Scanning dependencies of target SimGearScene
[ 46%] Building C object
simgear/CMakeFiles/SimGearScene.dir/canvas/ShivaVG/src/shArrays.c.o
In file included from
forget it was a mismatch with GL/gl.h
sorry for the noise
hello,
Linking CXX static library libSimGearCore.a
[ 46%] Built target SimGearCore
Scanning dependencies of target SimGearScene
[ 46%] Building C object
simgear/CMakeFiles/SimGearScene.dir/canvas/ShivaVG/src/shArrays.c.o
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'
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'
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
Just a heads-up. (MSVC10)
Alan
3 mathlib.c
3C:\FlightGear\simgear\simgear\nasal\mathlib.c(130): error C2143: syntax
error : missing ';' before 'type'
3C:\FlightGear\simgear\simgear\nasal\mathlib.c(131): error C2065: 'range' :
undeclared identifier
De: Alan Teeder
Just a heads-up. (MSVC10)
Alan
3 mathlib.c
3C:\FlightGear\simgear\simgear\nasal\mathlib.c(130): error C2143:
syntax error : missing ';' before 'type'
3C:\FlightGear\simgear\simgear\nasal\mathlib.c(131): error C2065:
'range' : undeclared identifier
discussions
Subject: Re: [Flightgear-devel] Simgear windows compile-
mathlib.c/test_state_machine
De: Alan Teeder
Just a heads-up. (MSVC10)
Alan
3 mathlib.c
3C:\FlightGear\simgear\simgear\nasal\mathlib.c(130): error C2143:
syntax error : missing ';' before 'type'
3C:\FlightGear\simgear
the course
the Parrot project follows.
-Original Message-
From: Frederic Bouvier
Sent: Wednesday, January 23, 2013 10:45 AM
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Simgear windows compile-
mathlib.c/test_state_machine
De: Alan Teeder
Just a heads-up
discussions
Subject: Re: [Flightgear-devel] Simgear windows compile-
mathlib.c/test_state_machine
De: Alan Teeder
Just a heads-up. (MSVC10)
Alan
3 mathlib.c
3C:\FlightGear\simgear\simgear\nasal\mathlib.c(130): error C2143:
syntax error : missing ';' before 'type'
3C
On 23 Jan 2013, at 11:45, Frederic Bouvier fredfgf...@free.fr wrote:
Reminder to all : MSVC is not C99 Compliant. It doesn't like C++ style
variable declaration inside the body of a bloc
I've pushed a fixed now, I would have fixed sooner but all the Windows slaves
on Jenkins are doing
From: James Turner
Sent: Wednesday, January 23, 2013 3:03 PM
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Simgear windows compile -
mathlib.c/test_state_machine
On 23 Jan 2013, at 11:45, Frederic Bouvier fredfgf...@free.fr wrote:
Reminder to all : MSVC
Hi James,
De: James Turner zakal...@mac.com
On 23 Jan 2013, at 11:45, Frederic Bouvier fredfgf...@free.fr
wrote:
Reminder to all : MSVC is not C99 Compliant. It doesn't like C++
style
variable declaration inside the body of a bloc
I've pushed a fixed now, I would have fixed
Simgear fails to build under MSVC10 today, 2012-11-28, with this error:
error C2724: 'SGThread::current' : 'static' should not be
used on member functions defined at file scope
file D:\Git_New\my_simgear\simgear\threads\SGThread.cxx
Line 84
Simpits
Vivian Meazza wrote:
Simgear fails to build under MSVC10 today, 2012-11-28, with this error:
error C2724: 'SGThread::current' : 'static' should not be
used on member functions defined at file scope
file
Just a heads up. The error report is :-
Alan
3 shContext.c
3C:\FlightGear\simgear\simgear\canvas\ShivaVG\src\shContext.c(37): error
C2491: 'vgCreateContextSH' : definition of dllimport function not allowed
3C:\FlightGear\simgear\simgear\canvas\ShivaVG\src\shContext.c(65): error
C2491:
Am 2012-11-05 12:14, schrieb Alan Teeder:
Just a heads up. The error report is :-
Thanks for the report. Should now be fixed.
Tom
--
Thomas Geymayer www.tomprogs.at / C-Forum und Tutorial: www.proggen.org
Student
-Original Message-
From: Thomas Geymayer
Sent: Monday, November 05, 2012 12:19 PM
To: flightgear-devel@lists.sourceforge.net
Subject: Re: [Flightgear-devel] Simgear/ShivaVG compile fails on windows
Am 2012-11-05 12:14, schrieb Alan Teeder:
Just a heads up. The error report
:Alan Teeder wrote
Am 2012-11-05 12:14, schrieb Alan Teeder:
Just a heads up. The error report is :-
Thanks for the report. Should now be fixed.
Tom
Yes - it all compiles and runs again. And my canvas HUD (in development)
still
works!
But mine doesn't :-(
Am 2012-11-05 16:02, schrieb Vivian Meazza:
But mine doesn't :-(
https://dl.dropbox.com/u/57645542/fgfs-screen-068.png
Any clues/hints?
Have you also updated fgdata? The way how the background color is set
has been changed (Now it uses only on single property for the whole
color instead of
On 5 Nov 2012, at 13:50, Alan Teeder wrote:
Yes - it all compiles and runs again. And my canvas HUD (in development)
still works!
Can you talk a little about the Canvas HUD? Moving the HUD to use the Canvas
would be a great step from my point of view, since it and 2D panels (which I am
-
From: James Turner
Sent: Monday, November 05, 2012 3:11 PM
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Simgear/ShivaVG compile fails on windows
On 5 Nov 2012, at 13:50, Alan Teeder wrote:
Yes - it all compiles and runs again. And my canvas HUD (in development)
still
Thomas wrote
fails on windows
Am 2012-11-05 16:02, schrieb Vivian Meazza:
But mine doesn't :-(
https://dl.dropbox.com/u/57645542/fgfs-screen-068.png
Any clues/hints?
Have you also updated fgdata?
Yes, using MSVC10, and after the same problems as Alan.
The way how the background
Am 2012-11-05 18:30, schrieb Vivian Meazza:
I'm using the Nasal API - it used to all work before today's update. Can't
really see what to change
Are you using canvas.setColorBackground(r, g, b, a) and is there a function
setColorBackground: func () { me.texture.getNode('background',
at the
time of posting.
Strange.
Alan
-Original Message-
From: Thomas Geymayer
Sent: Monday, November 05, 2012 5:52 PM
To: flightgear-devel@lists.sourceforge.net
Subject: Re: [Flightgear-devel] Simgear/ShivaVG compile fails on windows
Am 2012-11-05 18:30, schrieb Vivian Meazza:
I'm
Thomas wrote:
Am 2012-11-05 18:30, schrieb Vivian Meazza:
I'm using the Nasal API - it used to all work before today's update.
Can't really see what to change
Are you using canvas.setColorBackground(r, g, b, a)
I have this:
m.canvas.addPlacement(placement);
FYI the Atlas configure.ac will use -lSimGearCore if ENABLE_SIMGEAR_SHARED
is set to yes, which is misleading. I will change this to something more
more useful (Suggestion?).
I added ENABLE_SIMGEAR_SHARED to Atlas some time last year, since the
libraries SimGearCore and SimGearScene (the
Octobre 2012 18:26:54
Objet: [Flightgear-devel] Simgear commit breaks Atlas (ot??)
After SGTime: use SGGeod, quieter init. (James Turner
89d30acbc5040bf36a3329fcb21789d2855fa6d3)
Atlas build (misc.cxx) fails at:
double magneticVariation(double lat, double lon, double elev)
{
SGTime t1
...@btinternet.com
À: FlightGear devel flightgear-devel@lists.sourceforge.net
Envoyé: Dimanche 14 Octobre 2012 18:26:54
Objet: [Flightgear-devel] Simgear commit breaks Atlas (ot??)
After SGTime: use SGGeod, quieter init. (James Turner
89d30acbc5040bf36a3329fcb21789d2855fa6d3)
Atlas build
- Mail original -
De: Alasdair Campbell ali...@btinternet.com
À: FlightGear devel flightgear-devel@lists.sourceforge.net
Envoyé: Dimanche 14 Octobre 2012 18:26:54
Objet: [Flightgear-devel] Simgear commit breaks Atlas (ot??)
After SGTime: use SGGeod, quieter init. (James
On Sun, 14 Oct 2012 23:24:29 +0200 (CEST)
Frederic Bouvier fredfgf...@free.fr wrote:
Simgear library naming changed recently. -lsgmagvar -lsgtiming -lsgmisc
-lsgio -lsgserial -lsgdebug -lsgbucket -lsgstructure -lsgmath -lsgthreads
are gone and should be replaced by -lSimGearCore
Hi,
For some time, Simgear has had the option to build shared libraries (DLLs on
Windows) - this is only really useful for developers, since it can reduce link
times. However, when I made this change, I organised Simgear into 'core' and
'scene' libraries; the 'core' part is also what we call
James Turner wrote:
Mathias has suggested, and I agree, it would be sensible to also
package the *static* libraries this way. So instead of having many
static libraries, we will have only two: libSimGearCore.a and
libSimGearScene.a
Sounds good,
Martin.
--
Unix _IS_ user friendly
Hi,
I'm already linking all my deps dynamically against SG, but makeing it
easier for the static variant would be great as well. Even more so if you
take care of the TG changes :)
Cheers
Chris
James Turner wrote:
Hi,
For some time, Simgear has had the option to build shared libraries
Hi,
I cannot reproduce the problem, since I do not use MacPorts. IMHO we should
simply copy from OSG CMakeModules/FindZLIB.cmake to Simgear CMakeModules, in
order to force same semantics on OSG and Simgear.
Greetings
Olaf
Hi James
Didn’t dive into but noticed OSG has probably a more
Hi all
I had some problems compiling simgear release/2.6.0 using zlib 1.2.6 on
OSX. Looks like the main problem is here (independent of platform?):
lowlevel.hxx
void sgReadString ( gzFile fd, char **var ) ;
lowlevel.cxx
int c = gzgetc ( fd ) ;
While this seems to
On 28 Mar 2012, at 12:21, HB-GRAL wrote:
I had some problems compiling simgear release/2.6.0 using zlib 1.2.6 on
OSX. Looks like the main problem is here (independent of platform?):
lowlevel.hxx
void sgReadString ( gzFile fd, char **var ) ;
lowlevel.cxx
int
Am 28.03.12 15:08, schrieb James Turner:
The real issue is that we're finding zlib.h in /opt/local/include, but using
the libz from /usr. (The Apple supplied version)
I tried to find a solution, so that we use one header + library consistently,
but didn't yet figure this out. Since zlib
If I am understanding you correctly, you want to get access to various
variables within flightgear. Isn't the Property Tree via telnet or http
something that might work for you? Should be easy to access it from a web
service even. Or define a generic protocol, the wiki had an example how to
make
I'm looking at part of FG in various scenarious..
So Can I propose we expand the scope to the simgear code..
The intention would be to make available all the maths within simgear..
for all other langs//
Geoff has got the perl..
I got some python..
there's some java in openradar
and indeed I
On 25 Aug 2011, at 19:44, Alan Teeder wrote:
Well, that fixed the compilation, but at run time I see:
mismatch in socket address sizes
Error: connect() failed in make-client_socket()
Pushed a Simgear change to hopefully fix this, or at least give more
information when it fails - let me
: [Flightgear-devel] Simgear -netinfo/in.h notavailablefor
windows
On 25 Aug 2011, at 19:44, Alan Teeder wrote:
Well, that fixed the compilation, but at run time I see:
mismatch in socket address sizes
Error: connect() failed in make-client_socket()
Pushed a Simgear change to hopefully fix
On 26 Aug 2011, at 09:49, Alan Teeder wrote:
It compiles and run now, but I still see the error messages (mismatch in
socket address sizes etc... ) mentioned in yesterday´s post ;-(
You should be seeing a bit more debug information, about why it's failing -
relating to the size of
disabled.
Alan
-Original Message-
From: James Turner
Sent: Friday, August 26, 2011 10:30 AM
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Simgear -netinfo/in.h notavailablefor
windows
On 26 Aug 2011, at 09:49, Alan Teeder wrote:
It compiles and run now, but I still
On 26 Aug 2011, at 10:45, Alan Teeder wrote:
Here you are:-
mismatch in socket address sizes: got 28, expected 16
family: 23
Interesting, that's an IPX (as in, Novell Netware!) address - I've committed
some additional changes so we're IP4 only for the moment, IP6 can be added
fairly
Your latest fix seems to have cleared the error messages.
Thanks.
Alan
-Original Message-
From: James Turner
Sent: Friday, August 26, 2011 11:29 AM
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Simgear -netinfo/in.h notavailablefor
windows
On 26 Aug 2011
On 26 Aug 2011, at 12:21, Alan Teeder wrote:
Your latest fix seems to have cleared the error messages.
And, it works, I hope? :)
James
--
EMC VNX: the world's simplest storage, starting under $10K
The only unified
understand that MS had fixed this particular bug back in Windows 2000 days,
but it seems to have crept back in – on my system at least.
Alan
From: James Turner
Sent: Monday, August 22, 2011 10:36 AM
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Simgear - netinfo/in.h
On 25 Aug 2011, at 15:21, Alan Teeder wrote:
I understand that MS had fixed this particular bug back in Windows 2000 days,
but it seems to have crept back in – on my system at least.
Should be fixed (in a different way) by an imminent FG commit.
James
, 2011 3:21 PM
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Simgear - netinfo/in.h notavailablefor windows
James
With the latest I get link errors looking for freeaddrinf and getaddrinfo.
It is cured when I add Wsiapi.h to raw_socket.cxx.
i.e.
#if defined(WINSOCK)
# include
Sorry James, but the header says it all. ;-(
This link may help http://msdn.microsoft.com/en-us/library/ms740096.
Alan--
uberSVN's rich system and user administration capabilities and model
configuration take the
Thanks for the fix. That was quick !
Alan
From: Alan Teeder
Sent: Monday, August 22, 2011 9:23 AM
To: Flightgear-devel@lists.sourceforge.net
Subject: [Flightgear-devel] Simgear - netinfo/in.h not available for windows
Sorry James, but the header says it all. ;-(
This link may help http
On 22 Aug 2011, at 10:28, Alan Teeder wrote:
Thanks for the fix. That was quick !
But not sufficient - I've reverted the whole set of changes until I have a
chance to go over them again, since everything seems to have broken. Bah.
James
I just merged the release/2.4.0 branches up to tag version/2.4.0-final
into the master branch of SimGear and FlightGear.
The intention for the master branch of the two code repositories is to
always hold the current version.
For consistency, I'd like to have the same strategy on fgdata sometime
On Sun, 21 Aug 2011, Torsten Dreyer wrote:
I just merged the release/2.4.0 branches up to tag version/2.4.0-final
into the master branch of SimGear and FlightGear.
The intention for the master branch of the two code repositories is to
always hold the current version.
For consistency, I'd
* Flightgear-commitlogs -- Saturday 30 July 2011:
commit 3ac5ff0cac4dfecc62e6deb440bb0aa309ff42c9
Author: James Turner
Tweaks to HTTP code, in preparation for using it for metar - especially,
test code for proxies
-headerData X-Time: requestTime
On 30 Jul 2011, at 15:25, Melchior FRANZ wrote:
-headerData X-Time: requestTime \r\n;
And, ironically, going to break METAR proxy service ...
It's okay, that line will be making a recurrence elsewhere :)
James
Please see inline and below:
- Original Message -
Please see inline and below:
On Friday, May 27, 2011 05:23:59 PM Frederic Bouvier wrote:
AFAICS, MSVC2010 compiles current Git version without any problem.
The OP
doesn't say what version he is trying to build, but if I recall
Please see inline and below:
On Friday, May 27, 2011 05:23:59 PM Frederic Bouvier wrote:
AFAICS, MSVC2010 compiles current Git version without any problem. The OP
doesn't say what version he is trying to build, but if I recall correctly,
this error was fixed months ago. See
Hello all,
I am trying to build FG in Windows 7, using Visual Studio 10. A part of that
process is simgear, and that gives me some trouble...
I eliminated all compile errors with the exception of this one:
On Fri, 27 May 2011 12:55:24 -0400 (EDT), Claus wrote in message
1780160612.44750.1306515324059.javamail.r...@mail2.gatech.edu:
Hello all,
I am trying to build FG in Windows 7, using Visual Studio 10.
..ah. Historically, Microsoft has made use of it's tools and
tools to discourage the use
Arnt, different compilers often catch different subtle errors, so it is good
and healthy to run our code through a variety of compilers on a variety of
platforms. Gcc isn't perfect. Unfortunately I'm can't offer specific help
for this particular problem, but hopefully one of our other windows
Claus Christmann wrote
Hello all,
I am trying to build FG in Windows 7, using Visual Studio 10. A part of
that process is simgear, and that gives me some trouble...
I eliminated all compile errors with the exception of this one:
1c:\users\claus\desktop\flighgear-dependencies\simgear-
On Fri, 27 May 2011 14:21:20 -0500, Curtis wrote in message
banlktinc4gbt1hua7zg3vakekzm3b3p...@mail.gmail.com:
Arnt, different compilers often catch different subtle errors, so it
is good and healthy to run our code through a variety of compilers on
a variety of platforms. Gcc isn't
AFAICS, MSVC2010 compiles current Git version without any problem. The OP
doesn't say what version he is trying to build, but if I recall correctly, this
error was fixed months ago.
See
http://gitorious.org/fg/simgear/commit/acbc09b232e4570462d5936eaf20d2671530d8f4
Last tested Boost is 1.44.0
On Fri, 27 May 2011, Arnt Karlsen wrote:
On Fri, 27 May 2011 12:55:24 -0400 (EDT), Claus wrote in message
1780160612.44750.1306515324059.javamail.r...@mail2.gatech.edu:
Hello all,
I am trying to build FG in Windows 7, using Visual Studio 10.
..ah. Historically, Microsoft has made use of
On Fri, 27 May 2011, Vivian Meazza wrote:
Any ideas?
I'm still using boost 1.37.0 - it might be worth trying an earlier version
You know that we're using 1.44 currently, right?
g.
--
Proud owner of F-15C 80-0007
http://www.f15sim.com - The only one of its kind.
Gene
On Fri, 27 May 2011, Vivian Meazza wrote:
Any ideas?
I'm still using boost 1.37.0 - it might be worth trying an earlier
version
You know that we're using 1.44 currently, right?
I didn't know that - but boost 1.37 still works - I would normally upgrade
when it causes a
On Fri, 27 May 2011, Vivian Meazza wrote:
Gene
On Fri, 27 May 2011, Vivian Meazza wrote:
Any ideas?
I'm still using boost 1.37.0 - it might be worth trying an earlier
version
You know that we're using 1.44 currently, right?
I didn't know that - but boost 1.37 still works - I would
Hi,
..simgear(?) link error output, compile log link below:
make[3]: Leaving directory
`/home/arnt/FG-git/fgfs/flightgear/src/Traffic' make[2]: Leaving
directory `/home/arnt/FG-git/fgfs/flightgear/src/Traffic' Making
install in Main make[2]: Entering directory
On Sun, 2011-04-10 at 12:24 +0200, Arnt Karlsen wrote:
[snip]
error: undefined reference to
'osg::PagedLOD::removeExpiredChildren(double, int,
[snip]
Hi Arnt,
From your compile log, note the entry -
*..we use system's OSG-2.9.11-1. ;o) ***
and from your 'dpkg' display that is what you are
On Sun, Apr 10, 2011 at 12:24 PM, Arnt Karlsen a...@c2i.net wrote:
Hi,
..simgear(?) link error output, compile log link below:
in function vtable for
simgear::SGPagedLOD:SGPagedLOD.cxx(.rodata._ZTVN7simgear10SGPagedLODE+0x110):
error: undefined reference to
On 10.04.2011 13:29, Geoff McLane wrote:
As far as I am aware we can _NOT_ presently use
later that OSG-2.9.9 ;=((
Yes, we can. But 2.8.3 + 2.9.9 are used by the automatic download
compile script, since these versions are known to work fine. And as we
noticed, we have a lot of people running
On Sun, 2011-04-10 at 14:34 +0200, ThorstenB wrote:
As far as I am aware we can _NOT_ presently use
later that OSG-2.9.9 ;=((
Yes, we can.
Huh? Then WHY does Arnt have a LINK problem with OSG-2.9.11?
It always takes some days to adapt sg/fg to OSG changes, but right
now,
it compiles
On 10.04.2011 15:02, Geoff McLane wrote:
On Sun, 2011-04-10 at 14:34 +0200, ThorstenB wrote:
As far as I am aware we can _NOT_ presently use
later that OSG-2.9.9 ;=((
Yes, we can.
Huh? Then WHY does Arnt have a LINK problem with OSG-2.9.11?
I don't know. The error Arndt is seeing is a
On Sun, 10 Apr 2011 14:34:35 +0200, ThorstenB wrote in message
4da1a3db.8000...@gmail.com:
On 10.04.2011 13:29, Geoff McLane wrote:
As far as I am aware we can _NOT_ presently use
later that OSG-2.9.9 ;=((
Yes, we can. But 2.8.3 + 2.9.9 are used by the automatic download
compile
On Sun, 2011-04-10 at 19:24 +0200, Arnt Karlsen wrote:
... OSG-svn does not build on neither g++-4.6 nor g++-4.5,
which compiler version is used on the Hudson server?
Nor with my OLD g++ (GCC) 4.2.4 (Ubuntu 4.2.4-1ubuntu4) ;=))
Geoff.
1 - 100 of 378 matches
Mail list logo
