John Check wrote:
Theres nothing abot the licensing terms of the base package
that would prevent the scenario of which he speaks.
FWIW Erik, I understand how you feel, but OTOH thats the GPL.
Yep, GPL covers almost anything, but I'm not so sure LGPL does.
Erik
Norman Vine wrote:
FYI
http://www.boeing.com/news/releases/2002/q4/nr_021018m.html
Heh, the next thing will be to remove that glass shell in the front and
call it a AUV ...
Erik
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
Dear Jim,
I checked myself several times but cannot find a mistake at the moment. Somebody else
with a FEM package could check my calculations. I fiddled a bit around with the
constraints but these do not make much difference.
I also got your model running. It looks very nice indeed. The model
John Check writes:
Latest cvs build falls down with:
g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src
-I/usr/X11R6/include -g -O2 -D_REENTRANT -c -o pt_lights.o `test -f
'pt_lights.cxx' || echo './'`pt_lights.cxx
pt_lights.cxx: In function `ssgTimedSelector*
John Check writes:
g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src
-I/usr/X11R6/include -DPKGLIBDIR=\/usr/local/lib/FlightGear\ -g -O2
-D_REENTRANT -c -o main.o `test -f 'main.cxx' || echo './'`main.cxx
main.cxx:152: `void (*glPointParameterfEXT)(unsigned int,
On Fri, Oct 18, 2002 at 04:05:52PM -0400, David Megginson wrote:
Andy Ross writes:
The attached one-liner fixes the problem, but someone with more
knowlege should probably think of a better solution. We shouldn't be
initializing static state from within a member initializer. Maybe
On Fri, Oct 18, 2002 at 11:16:25PM -0400, John Check wrote:
On Friday 18 October 2002 11:02 pm, John Check wrote:
Latest cvs build falls down with:
g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src
-I/usr/X11R6/include -g -O2 -D_REENTRANT -c -o pt_lights.o `test -f
On Sat, Oct 19, 2002 at 08:53:54PM +1000, Simon Fowler wrote:
On Fri, Oct 18, 2002 at 11:16:25PM -0400, John Check wrote:
On Friday 18 October 2002 11:02 pm, John Check wrote:
Latest cvs build falls down with:
g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src
On Sat, Oct 19, 2002 at 09:55:46PM +1000, Simon Fowler wrote:
On Sat, Oct 19, 2002 at 08:53:54PM +1000, Simon Fowler wrote:
On Fri, Oct 18, 2002 at 11:16:25PM -0400, John Check wrote:
Okay now it dies with:
g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src
Simon Fowler wrote:
Actually, I just got the same error with (according to GL/gl.h) Mesa
3.4, so that's not it.
And it went away again, when I stopped defining GL_GLEXT_LEGACY . .
In Mesa 3.4's gl.h glPointParameterfvEXT is wrapped in a #ifdef
GL_GLEXT_LEGACY (as is glActiveTextureARB in
On Sat, 19 Oct 2002 11:18:34 +0200,
Marcel Wittebrood [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]:
Dear Jim,
I checked myself several times but cannot find a mistake at the
moment. Somebody else with a FEM package could check my calculations.
..is not going to happen unless
John Check wrote:
Latest cvs build falls down with:
pt_lights.cxx:304: `cout' undeclared (first use this function)
You're using gcc 3.2 I assume? It's a namespace issue. The C++
standard library naming is stricter now. You need to use std::cout,
or insert a using namespace std; above the
Andy Ross writes:
John Check wrote:
main.cxx:153:
void (*glPointParameterfvEXT)(unsigned int, const GLfloat*)
/usr/X11R6/include/GL/gl.h:2520:
glPointParameterfvEXT(unsigned int, const GLfloat*)'
OK, this one looks kinda wrong. Our code is defining its own copy of
the
diff -u -w -r1.31 main.cxx
--- main.cxx17 Oct 2002 04:34:32 - 1.31
+++ main.cxx19 Oct 2002 18:38:22 -
@@ -141,16 +141,16 @@
typedef void (APIENTRY * PFNGLPOINTPARAMETERFVEXTPROC)(GLenum pname,
const GLfloat *params);
[Er, oops. The last one had the patch but not the text. Apologies!]
OK, looking more carefully, I think I see how this is supposed to
work. Because not all OpenGL implementations export the
PointParameter functions, Curt is using function pointers and the
GetProcAddress stuff.
This is fine;
On Friday 18 October 2002 09:17 pm, David Megginson wrote:
John Check writes:
The last time we had KSFO with lights in there it had some problems
too. I think it's worth the tradeoff but if you think it's going
to break anything I can hold off.
I'd prefer to put in a complete rebuild
William L. Riley writes:
unlurk
I have been busy lately (who hasn't?) but can find the time to do a base
Scenery rebuild. What is the status of the lighting? Should I do a rebuild
this weekend? I'll have to check the back messages as I haven't been
following along as closely as I
Hi
having played around a little bit with flightgrear earlier this year,
I got really hooked since 0.8.0 came out. Good work guys... :)
A couple of questions have popped up in my mind about some
things... (some are especially interesting for cockpit builders :-)
Is it possible to have (or
On Saturday 19 October 2002 1:33 pm, Andy Ross wrote:
John Check wrote:
Latest cvs build falls down with:
pt_lights.cxx:304: `cout' undeclared (first use this function)
You're using gcc 3.2 I assume? It's a namespace issue. The C++
standard library naming is stricter now. You need
On Saturday 19 October 2002 03:30 pm, [EMAIL PROTECTED] wrote:
It would be wise to wait a week or two before doing a complete rebuild
of the scenery, in case Curt needs to change anything, but a rebuild
of w130n30 (or at least the area around KSFO) would be very welcome
this weekend.
I am
John Check wrote:
[snip]
So, my question is, is anybody planning on attending the show
and/or willing to do some booth time? It's not necessarily the
deciding factor in the long run, but I don't want to wait too long
to register.
TTYL
J
___
On Saturday 19 October 2002 6:03 pm, William Earnest wrote:
John Check wrote:
[snip]
So, my question is, is anybody planning on attending the show
and/or willing to do some booth time? It's not necessarily the
deciding factor in the long run, but I don't want to wait too long
to
On Saturday 19 October 2002 2:47 pm, Andy Ross wrote:
[Er, oops. The last one had the patch but not the text. Apologies!]
OK, looking more carefully, I think I see how this is supposed to
work. Because not all OpenGL implementations export the
PointParameter functions, Curt is using
The base scenery package was rebuilt tonight and is available for download.
http://www.randdtechnologies.com/fgfs/newScenery/
The rebuild went very smoothly so there is probably some huge glaring error
that I missed. ;)
Wm
--
William L. Riley
[EMAIL PROTECTED]
On Saturday 19 October 2002 7:42 pm, William L. Riley wrote:
The base scenery package was rebuilt tonight and is available for download.
http://www.randdtechnologies.com/fgfs/newScenery/
The rebuild went very smoothly so there is probably some huge glaring error
that I missed. ;)
Wm
On Sat, 19 Oct 2002 18:45:15 -0400,
John Check [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]:
On Saturday 19 October 2002 6:03 pm, William Earnest wrote:
Of possible relevance, does anyone have an idea for FlightGear
might
perform on a laptop with an ATI Mobility Radeon
On Saturday 19 October 2002 7:42 pm, William L. Riley wrote:
The base scenery package was rebuilt tonight and is available for download.
http://www.randdtechnologies.com/fgfs/newScenery/
The rebuild went very smoothly so there is probably some huge glaring error
that I missed. ;)
Wm
Looks
John Check wrote:
Is this last line correct?
Uh, no. :)
Sorry. I don't compile on a windows box, so that part of the change
was blind.
Obviously, the actual names of the symbols used isn't important. You
could just as easily use GL or fg, or fgfsgl or whatnot so long
as it's consistent and
On Saturday 19 October 2002 8:52 pm, Andy Ross wrote:
John Check wrote:
Is this last line correct?
Uh, no. :)
Sorry. I don't compile on a windows box, so that part of the change
was blind.
windows box? I don't like the way they look. Shutters are okay,
but windowboxes.. not my thing.
29 matches
Mail list logo
