RE: [Flightgear-devel] Problem with final linking - Solved!
> I don't expect anyone to deal with running FlightGear under Cygnus' X, > right? Besides, this sure isn't worth a lot of trouble with the > Cygwin gang. > We just should keep in mind there's a problem and add a note in the proper > places (I'll do so in the next version of the Getting Started). > > Sure, a better solution might be having the configure scripts detecting X > being installed in conjunction with Cygwin and spitting a corresonding > message. It souldn't be too hard (I recall at least the PLIB configure > script noted the X libs being found as such). Gents, As a Cygwin developer, I don't want or need to run FGFS under X, but I would like to be able to work on it with X present, without using it. It would be "worth it" to be able to configure FGFS with "--without-X" or something similar on a Cygwin system (or automatically not use X on Cygwin). Now that XFree86, Qt, KDE, etc. are available for Cygwin (and stable) I think you will find developers wanting to have X peacefully coexist with FGFS on their Cygwin systems. Regards, Paul Paul R. Deppe Veridian Engineering (formerly Calspan) Flight & Aerospace Research Group 150 North Airport Drive Buffalo, NY 14225 (716) 631-6898 (716) 631-6990 FAX [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
AW: [Flightgear-devel] Problem with final linking - Solved!
Norman, > Since 'X' has just VERY recently been added as an option to the > Cygwin Installer the fallout from this has not hit the Cygwin list yet > and having been 'toasted' once there over this issue I am hesitant > to bring it up again > So I have a suspicion that we will have to find our own way around > this issue or we might have to run an X Server just to develop FGFS > in a 'standard' Cygwin enviroment :-( I don't expect anyone to deal with running FlightGear under Cygnus' X, right? Besides, this sure isn't worth a lot of trouble with the Cygwin gang. We just should keep in mind there's a problem and add a note in the proper places (I'll do so in the next version of the Getting Started). Sure, a better solution might be having the configure scripts detecting X being installed in conjunction with Cygwin and spitting a corresonding message. It souldn't be too hard (I recall at least the PLIB configure script noted the X libs being found as such). Regards, Michael -- Michael Basler, Jena, Germany [EMAIL PROTECTED] http://www.geocities.com/pmb.geo/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Problem with final linking - Solved!
Michael Basler wites: > I had the X windows package coming with Cygwin installed. >This includes different opengl/glut packages adapted for >X, which - expectedly - do not work out of the box with FlightGear. > >Thus, the lesson to learn is: Do NOT install X windows while building >FlightGear under Cygwin (at least not until a more clever >solution can be found). This will probably take a while to sort out as a lot of projects not just FGFS and PLib use a simple autoconf test if 'X' is present assume we are on a Unix Machine Since 'X' has just VERY recently been added as an option to the Cygwin Installer the fallout from this has not hit the Cygwin list yet and having been 'toasted' once there over this issue I am hesitant to bring it up again FWIW Every other time a layout conflict in Cygwin between what 'X' expects and what a Unix program running on top of native WIN32 expects, the 'X' way has prevailed. So I have a suspicion that we will have to find our own way around this issue or we might have to run an X Server just to develop FGFS in a 'standard' Cygwin enviroment :-( Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
AW: [Flightgear-devel] Problem with final linking - Solved!
Dear Norman, > The opengl libs got moved to > > / lib / w32api / directory > > don't ask me why ? > > I just made a link to these in my '/ lib' dirrectory I solved it as follows: Meanwhile, I had the X windows package coming with Cygwin installed. This includes different opengl/glut packages adapted for X, which - expectedly - do not work out of the box with FlightGear. Thus, the lesson to learn is: Do NOT install X windows while building FlightGear under Cygwin (at least not until a more clever solution can be found). Cameron, maybe we could throw this into the FAQ? After uninstalling X, I did not have to shift/link any other libraries. Thanks and regards, Michael -- Michael Basler, Jena, Germany [EMAIL PROTECTED] http://www.geocities.com/pmb.geo/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Problem with final linking
Michael Basler writes: > >> You have exactly the same errors on screen as I reported friday in my >> openGL question :-) It seems to be a cygwin related problem. > >Thank for keeping an eye on it. > >I returend from opengl 1.1.06 to 1.1.05, but this did not yet >help either. > >Norman, I think you have "close relations" to the cygwin >crew. Could you >have a look upon this? Thanks a lot. Michael The opengl libs got moved to / lib / w32api / directory don't ask me why ? I just made a link to these in my '/ lib' dirrectory you could also just copy them there or add a -mwindows flag to the gcc link options IMHO None of the above are the right solution but I have quit pushing for what IMHO is the 'right' way of doing things in Open Source projects when one can easily change things in your local copy If-I-wanted-to-be-borg-I-wouldn't-need-a-compiler'ly yrs Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
AW: [Flightgear-devel] Problem with final linking
Marcel, > You have exactly the same errors on screen as I reported friday in my > openGL question :-) It seems to be a cygwin related problem. Thank for keeping an eye on it. I returend from opengl 1.1.06 to 1.1.05, but this did not yet help either. Norman, I think you have "close relations" to the cygwin crew. Could you have a look upon this? Thanks a lot. Regards, Michael -- Michael Basler, Jena, Germany [EMAIL PROTECTED] http://www.geocities.com/pmb.geo/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Problem with final linking
age: 5
Date: Sun, 21 Apr 2002 20:24:35 -0500
From: Jonathan Polley <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: [Flightgear-devel] JSBSim and FlightGear 0.7.10
Reply-To: [EMAIL PROTECTED]
Due to some problems that MSVC has with how FlightGear uses overloading,
I
still have private copies of a hand full of JSBSim files. Will that be
fixed in 0.7.10?
As a refresher, MSVC has a problem with functions like the following,
overloaded, definitions when they are used in a call to, the
overloaded,
Tie() function.
FGColumnVector3& GetMoments(void) { return vMoments; }
double GetMoments(int idx) const { return vMoments(idx); }
I have added a _V to the end of the vector versions to make MSVC happy,
but that was not the consensus when the problem appeared.
Thanks,
Jonathan Polley
--__--__--
Message: 6
Date: Mon, 22 Apr 2002 02:32:26 -
To: <[EMAIL PROTECTED]>
From: "Jim Wilson" <[EMAIL PROTECTED]>
Subject: [Flightgear-devel] Model lighting
Reply-To: [EMAIL PROTECTED]
One idea I had to model a blinking light on an aircraft is to use spin
animation
on a poly that has emmisive properties. I'm thinking that this could be
tied
somehow to the be tied to /sim/time/elapsed-time, but I'm not sure how.
David, can this be done with the current code?
Also, I noticed that in ac3d you can define a point of light
(omnidirectional
source) which could be somewhat useful in providing light emiting from
the
aircraft onto the runway (not extremely realistic, but better than
nothing).
When trying this however, it appears that plib doesn't do anything with
the
ac3dlight objects. Is this a plib problem and/or should we be doing
this
some other way anyway?
Best,
Jim
--__--__--
Message: 7
Date: Mon, 22 Apr 2002 09:07:18 +0200
From: "Marcel Wittebrood" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Subject: [Flightgear-devel] Strange opengl compiler error ?
Reply-To: [EMAIL PROTECTED]
Thanks Julian,
I have a ATI M-4 graphix card that is indeed not the fastest available
but does have some 3D-acceleration (An Opengl TAB is available in the
screen properties (adapter, next advanced).
I think this means that a pre-compiled flight-gear (thus a binary) will
sometimes show strange behaviour on our systems.
kind regards
--__--__--
Message: 8
From: "Michael Basler" <[EMAIL PROTECTED]>
To: "Flightgear-Devel" <[EMAIL PROTECTED]>
Date: Mon, 22 Apr 2002 12:20:18 +0200
Subject: [Flightgear-devel] Problem with final linking
Reply-To: [EMAIL PROTECTED]
Hi,
could any one tell me why the most recent CVS of PLIB/Simgear/FlightGear
from today does not do the final linking? I don't recall having seen
this on
the list before?
This is (a recently updated) Cygwin under Win XP.
Thanks and
Regards, Michael
--
make[2]: Entering directory `/usr/local/source/flightgear/src/Main'
c++ -DPKGLIBDIR=\"/usr/local/FlightGear/lib/FlightGear\" -g -O2
-L/usr/local
/lib
-o fgfs main.o fg_commands.o fg_init.o fg_io.o fg_props.o fgfs.o
globals.o
log
ger.o options.o splash.o viewer.o viewmgr.o location.o
../../src/Aircraft/libAir
craft.a ../../src/ATC/libATC.a
../../src/Autopilot/libAutopilot.a
../..
/src/Cockpit/libCockpit.a ../../src/Cockpit/built_in/libBuilt_in.a
../../s
rc/Controls/libControls.a ../../src/FDM/libFlight.a
../../src/FDM/Ba
lloon/libBalloon.a ../../src/FDM/JSBSim/libJSBSim.a
../../src/FDM/YA
Sim/libYASim.a ../../src/FDM/JSBSim/filtersjb/libfiltersjb.a
../../src/FDM/La
RCsim/libLaRCsim.a ../../src/FDM/UIUCModel/libUIUCModel.a
../../src/GUI/li
bGUI.a ../../src/Model/libModel.a ../../src/Navaids/libNavaids.a
../../sr
c/Scenery/libScenery.a ../../src/Sound/libSound.a
../../src/Airports/libAi
rports.a ../../src/Network/libNetwork.a
../../src/NetworkOLK/lib
NetworkOLK.a../../src/Objects/libObjects.a ../../src/Time/libTime.a
../../s
rc/WeatherCM/libWeatherCM.a
../../src/Input/libInput.a -lsgroute -lsgsk
y -lsgephem -lsgtiming -lsgio -lsgscreen-lsgmath -lsgbucket
-lsgdebu
g -l
sgmagvar -lsgmisc -lsgxml -lsgserial -lplibpu
-lplibfnt -
lpli
bnet -lplibssg -lplibsg -lmk4 -lz -lpthread -lm -lglut32
-lgl
u32
-lopengl32 -luser32 -lgdi32 -lplibsl -lplibsm -lwinmm -lplibul -lm
Warning: resolving _glBlendFunc by linking to _glBlendFunc@8
Use --enable-stdcall-fixup to disable these warnings
Use --disable-stdcall-fixup to disable these fixups
Warning: resolving _glPopAttrib by linking to _glPopAttrib@0
Warning: resolving _glPushAttrib by linking to _glPushAttrib@4
Warning: resolving _glDisable by linking to _glDisable@4
Warning: resolving _glPopMatrix by linking to _glPopMatrix@0
Warning: resolving _glOrtho by linking to _glOrtho@48
Warning: resolving _glPushMatrix by linking to _glPushMatrix@0
Warning: resolving _glPixelStorei by linking to _glPixelStorei@8
Warning: resolv
[Flightgear-devel] Problem with final linking
Hi, could any one tell me why the most recent CVS of PLIB/Simgear/FlightGear from today does not do the final linking? I don't recall having seen this on the list before? This is (a recently updated) Cygwin under Win XP. Thanks and Regards, Michael -- make[2]: Entering directory `/usr/local/source/flightgear/src/Main' c++ -DPKGLIBDIR=\"/usr/local/FlightGear/lib/FlightGear\" -g -O2 -L/usr/local /lib -o fgfs main.o fg_commands.o fg_init.o fg_io.o fg_props.o fgfs.o globals.o log ger.o options.o splash.o viewer.o viewmgr.o location.o ../../src/Aircraft/libAir craft.a ../../src/ATC/libATC.a ../../src/Autopilot/libAutopilot.a ../.. /src/Cockpit/libCockpit.a ../../src/Cockpit/built_in/libBuilt_in.a ../../s rc/Controls/libControls.a ../../src/FDM/libFlight.a ../../src/FDM/Ba lloon/libBalloon.a ../../src/FDM/JSBSim/libJSBSim.a ../../src/FDM/YA Sim/libYASim.a ../../src/FDM/JSBSim/filtersjb/libfiltersjb.a ../../src/FDM/La RCsim/libLaRCsim.a ../../src/FDM/UIUCModel/libUIUCModel.a ../../src/GUI/li bGUI.a ../../src/Model/libModel.a ../../src/Navaids/libNavaids.a ../../sr c/Scenery/libScenery.a ../../src/Sound/libSound.a ../../src/Airports/libAi rports.a ../../src/Network/libNetwork.a ../../src/NetworkOLK/lib NetworkOLK.a../../src/Objects/libObjects.a ../../src/Time/libTime.a ../../s rc/WeatherCM/libWeatherCM.a ../../src/Input/libInput.a -lsgroute -lsgsk y -lsgephem -lsgtiming -lsgio -lsgscreen-lsgmath -lsgbucket -lsgdebu g -l sgmagvar -lsgmisc -lsgxml -lsgserial -lplibpu -lplibfnt - lpli bnet -lplibssg -lplibsg -lmk4 -lz -lpthread -lm -lglut32 -lgl u32 -lopengl32 -luser32 -lgdi32 -lplibsl -lplibsm -lwinmm -lplibul -lm Warning: resolving _glBlendFunc by linking to _glBlendFunc@8 Use --enable-stdcall-fixup to disable these warnings Use --disable-stdcall-fixup to disable these fixups Warning: resolving _glPopAttrib by linking to _glPopAttrib@0 Warning: resolving _glPushAttrib by linking to _glPushAttrib@4 Warning: resolving _glDisable by linking to _glDisable@4 Warning: resolving _glPopMatrix by linking to _glPopMatrix@0 Warning: resolving _glOrtho by linking to _glOrtho@48 Warning: resolving _glPushMatrix by linking to _glPushMatrix@0 Warning: resolving _glPixelStorei by linking to _glPixelStorei@8 Warning: resolving _glMatrixMode by linking to _glMatrixMode@4 Warning: resolving _glViewport by linking to _glViewport@16 Warning: resolving _glGetIntegerv by linking to _glGetIntegerv@8 Warning: resolving _glLoadIdentity by linking to _glLoadIdentity@0 /usr/local/lib/libsgscreen.a(screen-dump.o): In function `sg_glDumpWindow(char c onst *, int, int)': /usr/local/source/simgear/simgear/screen/screen-dump.cxx:84: undefined reference to `glFinish' /usr/local/source/simgear/simgear/screen/screen-dump.cxx:86: undefined reference to `glReadPixels' /usr/local/lib/libsgscreen.a(tr.o): In function `trEndTile(_TRctx *)': /usr/local/source/simgear/simgear/screen/tr.cxx:404: undefined reference to `glF lush' /usr/local/source/simgear/simgear/screen/tr.cxx:418: undefined reference to `glR eadPixels' /usr/local/source/simgear/simgear/screen/tr.cxx:437: undefined reference to `glR eadPixels' /usr/local/lib/libsgscreen.a(tr.o): In function `trRasterPos3f(_TRctx *, float, -- Michael Basler, Jena, Germany [EMAIL PROTECTED] http://www.geocities.com/pmb.geo/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
