Board index FlightGear Support Compiling

Flightgear source code terminates in GLExtension.cpp

Building FlightGear from source, and in the need for help?

Flightgear source code terminates in GLExtension.cpp

Postby sathish » Mon Aug 27, 2018 10:56 am

Hi..
I have downloaded flightgear 2017.3.1 source code and OSG 3.4.0 version and compiled it on ubuntu 16.04 OS....but i am not able to run the source code because it is coming out while loading splash screen itself stating
Break @ address "0x1dc4d41" with no debug information available, or outside of program code.
at extensionSet.insert() function in GLExtension.cpp file.

IDE : Eclipse oxygen

ie, when the code is trying to access the below line it is terminating..
osg::isGLExtensionOrVersionSupported (contextID=0, extension=0x1dc4e2c,"GL_ARB_shader_objects");


Plz can any one help me how to make it run..
thanks in advance
sathish
 
Posts: 16
Joined: Tue Mar 13, 2018 12:51 pm

Re: Flightgear source code terminates in GLExtension.cpp

Postby wkitty42 » Thu Aug 30, 2018 5:19 pm

why 2017.3.1?
how are you building the code? download_and_compile.sh script or something else?
what is your video card?
what OpenGL do you have installed?
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 4641
Joined: Fri Feb 20, 2015 3:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 14.04.5

Re: Flightgear source code terminates in GLExtension.cpp

Postby sathish » Sat Sep 01, 2018 9:56 am

Hi..thanx
Is there any issue with 2017.3.1 version? because when i started working this was the latest so i downloaded.
using eclipse IDE i am compiling and it builded with no errors.
GeForce TITAN X card is my video card and i got getGLversionNumber as 4.99 when i debug the code and GLversion as 4.6.0 NVIDIA 390.25
what is the minimum required gl version for 2017.3.1?
i am not using the download_and_compile.sh script for compiling.
I have totaaly messed with this,can you help me.
what is the GL version supported by FG 2017.3.1..........?
sathish
 
Posts: 16
Joined: Tue Mar 13, 2018 12:51 pm

Re: Flightgear source code terminates in GLExtension.cpp

Postby wkitty42 » Sat Sep 01, 2018 4:37 pm

sathish wrote in Sat Sep 01, 2018 9:56 am:Is there any issue with 2017.3.1 version? because when i started working this was the latest so i downloaded.

other than it being like 2 versions old, no... we're fixing to be cutting 2018.3.1 RCs in another few days and then several weeks of testing them before the official release...

sathish wrote in Sat Sep 01, 2018 9:56 am:using eclipse IDE i am compiling and it builded with no errors.

ok...

sathish wrote in Sat Sep 01, 2018 9:56 am:GeForce TITAN X card is my video card and i got getGLversionNumber as 4.99 when i debug the code and GLversion as 4.6.0 NVIDIA 390.25
what is the minimum required gl version for 2017.3.1?

i have OpenGL 4.5.0 on this linux box... i do not recall what the minimum is but your's should be fine...

what Qt do you have installed? do you have all the required Qt libs installed, too?

i may need to point one of the devs to this topic but if we can get all the necessary info first, that'll be a help...
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 4641
Joined: Fri Feb 20, 2015 3:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 14.04.5

Re: Flightgear source code terminates in GLExtension.cpp

Postby sathish » Mon Sep 03, 2018 4:43 am

Hi..
I have installed Qt5 but i am not using it...i have disabled Qt5 in cmake configuration file and i am not merging the Qt related files in to my source code.
Is it necessary to add Qt libs?
sathish
 
Posts: 16
Joined: Tue Mar 13, 2018 12:51 pm

Re: Flightgear source code terminates in GLExtension.cpp

Postby wkitty42 » Mon Sep 03, 2018 5:54 pm

i think Qt5 is the minimum and needed for the built-in launcher... if you don't want/need the new launcher, disabling Qt should prevent it from being built...

disabling Qt may also affect the in-sim Aircraft Center... there are instructions somewhere (wiki?) on what to change in the sources to use the old Aircraft Center if it is desired in one's FG... it is only a coupld of lines, IIRC...

the newer Aircraft Center, while still experimental, is basically the launcher with some options disabled... it is still in development, though... i just tried it on the first 2018.3 Release Candidate and have a bug to report ;)

i have also just posted this to the developer's mailing list... hopefully someone will drop by soon with some more assistance...
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 4641
Joined: Fri Feb 20, 2015 3:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 14.04.5

Re: Flightgear source code terminates in GLExtension.cpp

Postby wkitty42 » Mon Sep 03, 2018 7:27 pm

sathish wrote in Mon Aug 27, 2018 10:56 am:I have downloaded flightgear 2017.3.1 source code and OSG 3.4.0 version and compiled it on ubuntu 16.04 OS...

does the above mean that you are building OSG as well as SG (SimGear) and FG (FlightGear) OR is that OSG that comes with Ubuntu 16.04?
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 4641
Joined: Fri Feb 20, 2015 3:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 14.04.5

Re: Flightgear source code terminates in GLExtension.cpp

Postby sathish » Tue Sep 04, 2018 9:21 am

I am building OSG,SG(SimGear) and Flightgear. i am not using OSG as dll.
sathish
 
Posts: 16
Joined: Tue Mar 13, 2018 12:51 pm

Re: Flightgear source code terminates in GLExtension.cpp

Postby wkitty42 » Tue Sep 04, 2018 1:16 pm

what does "ldd fgfs" turn up? is it linking against and using the libraries you expect it to be using?

eg:
Code: Select all
$ cat ~/flightgear-dev/next/ldd_fgfs.sh
#!/bin/bash
cd $(dirname $0)
cd install/flightgear/bin
export LD_LIBRARY_PATH=/opt/qt59/lib/x86_64-linux-gnu:/opt/qt59/lib:../../simgear/lib:../../openscenegraph/lib:../../openrti/lib:../../plib/lib
export OSG_NOTIFY_LEVEL=DEBUG
ldd ./fgfs

$ ~/flightgear-dev/next/ldd_fgfs.sh
        linux-vdso.so.1 =>  (0x00007fff35048000)
        libopenal.so.1 => /usr/lib/x86_64-linux-gnu/libopenal.so.1 (0x00007f183caa0000)
        libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x00007f183c858000)
        libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x00007f183c520000)
        libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x00007f183c308000)
        libGL.so.1 => /usr/lib/nvidia-384/libGL.so.1 (0x00007f183c060000)
        libosgTextd.so.131 => ../../openscenegraph/lib/libosgTextd.so.131 (0x00007f183bd10000)
        libosgSimd.so.131 => ../../openscenegraph/lib/libosgSimd.so.131 (0x00007f183b930000)
        libosgDBd.so.131 => ../../openscenegraph/lib/libosgDBd.so.131 (0x00007f183b3f0000)
        libosgParticled.so.131 => ../../openscenegraph/lib/libosgParticled.so.131 (0x00007f183b110000)
        libosgUtild.so.131 => ../../openscenegraph/lib/libosgUtild.so.131 (0x00007f183a918000)
        libosgViewerd.so.131 => ../../openscenegraph/lib/libosgViewerd.so.131 (0x00007f183a500000)
        libosgGAd.so.131 => ../../openscenegraph/lib/libosgGAd.so.131 (0x00007f183a208000)
        libosgd.so.131 => ../../openscenegraph/lib/libosgd.so.131 (0x00007f18399b8000)
        libOpenThreadsd.so.20 => ../../openscenegraph/lib/libOpenThreadsd.so.20 (0x00007f18397a8000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f1839588000)
        libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f1839368000)
        librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f1839160000)
        libcurl-gnutls.so.4 => /usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4 (0x00007f1838ef8000)
        libQt5Widgets.so.5 => /opt/qt59/lib/libQt5Widgets.so.5 (0x00007f18388a8000)
        libQt5Quick.so.5 => /opt/qt59/lib/libQt5Quick.so.5 (0x00007f1838440000)
        libQt5Gui.so.5 => /opt/qt59/lib/libQt5Gui.so.5 (0x00007f1837ed0000)
        libQt5Qml.so.5 => /opt/qt59/lib/libQt5Qml.so.5 (0x00007f1837ac0000)
        libQt5Network.so.5 => /opt/qt59/lib/libQt5Network.so.5 (0x00007f183cd60000)
        libQt5Core.so.5 => /opt/qt59/lib/libQt5Core.so.5 (0x00007f1837580000)
        libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f1837278000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f1836f70000)
        libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f1836d58000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f1836988000)
        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f1836780000)
        libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x00007f1836560000)
        libcgmanager.so.0 => /lib/x86_64-linux-gnu/libcgmanager.so.0 (0x00007f1836340000)
        libnih.so.1 => /lib/x86_64-linux-gnu/libnih.so.1 (0x00007f1836128000)
        libnih-dbus.so.1 => /lib/x86_64-linux-gnu/libnih-dbus.so.1 (0x00007f1835f18000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f183cd00000)
        libGLX.so.0 => /usr/lib/nvidia-384/libGLX.so.0 (0x00007f1835ce8000)
        libGLdispatch.so.0 => /usr/lib/nvidia-384/libGLdispatch.so.0 (0x00007f1835a18000)
        libXrandr.so.2 => /usr/lib/x86_64-linux-gnu/libXrandr.so.2 (0x00007f1835808000)
        libidn.so.11 => /usr/lib/x86_64-linux-gnu/libidn.so.11 (0x00007f18355d0000)
        librtmp.so.0 => /usr/lib/x86_64-linux-gnu/librtmp.so.0 (0x00007f18353b0000)
        libgcrypt.so.11 => /lib/x86_64-linux-gnu/libgcrypt.so.11 (0x00007f1835130000)
        libgnutls.so.26 => /usr/lib/x86_64-linux-gnu/libgnutls.so.26 (0x00007f1834e70000)
        libgssapi_krb5.so.2 => /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 (0x00007f1834c28000)
        liblber-2.4.so.2 => /usr/lib/x86_64-linux-gnu/liblber-2.4.so.2 (0x00007f1834a18000)
        libldap_r-2.4.so.2 => /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 (0x00007f18347c0000)
        libpng12.so.0 => /lib/x86_64-linux-gnu/libpng12.so.0 (0x00007f1834598000)
        libicui18n.so.52 => /usr/lib/x86_64-linux-gnu/libicui18n.so.52 (0x00007f1834190000)
        libicuuc.so.52 => /usr/lib/x86_64-linux-gnu/libicuuc.so.52 (0x00007f1833e10000)
        libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x00007f1833b08000)
        libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 (0x00007f1833900000)
        libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007f18336f8000)
        libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 (0x00007f18334e0000)
        libXrender.so.1 => /usr/lib/x86_64-linux-gnu/libXrender.so.1 (0x00007f18332d0000)
        libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x00007f18330c8000)
        libtasn1.so.6 => /usr/lib/x86_64-linux-gnu/libtasn1.so.6 (0x00007f1832eb0000)
        libp11-kit.so.0 => /usr/lib/x86_64-linux-gnu/libp11-kit.so.0 (0x00007f1832c68000)
        libkrb5.so.3 => /usr/lib/x86_64-linux-gnu/libkrb5.so.3 (0x00007f1832998000)
        libk5crypto.so.3 => /usr/lib/x86_64-linux-gnu/libk5crypto.so.3 (0x00007f1832768000)
        libcom_err.so.2 => /lib/x86_64-linux-gnu/libcom_err.so.2 (0x00007f1832560000)
        libkrb5support.so.0 => /usr/lib/x86_64-linux-gnu/libkrb5support.so.0 (0x00007f1832350000)
        libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x00007f1832130000)
        libsasl2.so.2 => /usr/lib/x86_64-linux-gnu/libsasl2.so.2 (0x00007f1831f10000)
        libgssapi.so.3 => /usr/lib/x86_64-linux-gnu/libgssapi.so.3 (0x00007f1831cd0000)
        libicudata.so.52 => /usr/lib/x86_64-linux-gnu/libicudata.so.52 (0x00007f1830460000)
        libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007f1830220000)
        libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 (0x00007f1830018000)
        libkeyutils.so.1 => /lib/x86_64-linux-gnu/libkeyutils.so.1 (0x00007f182fe10000)
        libheimntlm.so.0 => /usr/lib/x86_64-linux-gnu/libheimntlm.so.0 (0x00007f182fc00000)
        libkrb5.so.26 => /usr/lib/x86_64-linux-gnu/libkrb5.so.26 (0x00007f182f978000)
        libasn1.so.8 => /usr/lib/x86_64-linux-gnu/libasn1.so.8 (0x00007f182f6d0000)
        libhcrypto.so.4 => /usr/lib/x86_64-linux-gnu/libhcrypto.so.4 (0x00007f182f498000)
        libroken.so.18 => /usr/lib/x86_64-linux-gnu/libroken.so.18 (0x00007f182f280000)
        libwind.so.0 => /usr/lib/x86_64-linux-gnu/libwind.so.0 (0x00007f182f050000)
        libheimbase.so.1 => /usr/lib/x86_64-linux-gnu/libheimbase.so.1 (0x00007f182ee40000)
        libhx509.so.5 => /usr/lib/x86_64-linux-gnu/libhx509.so.5 (0x00007f182ebf0000)
        libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 (0x00007f182e930000)
        libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1 (0x00007f182e6f0000)


i use the download_and_compile.sh script for my builds... since i'm also on Ubuntu 14.04.5, i have to link against my own Qt since i want the launcher so i pull my Qt from a launchpad repo... that's why you can see my Qt libraries in /opt/qt59... i definitely build my own OSG which i get from the OSG git repo... it is branch OpenSceneGraph-3.4 which is actually OSG 3.4.2 at this time... you can also see that i am linking against my NVIDIA drivers...
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 4641
Joined: Fri Feb 20, 2015 3:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 14.04.5

Re: Flightgear source code terminates in GLExtension.cpp

Postby Hooray » Wed Sep 05, 2018 6:20 am

I may be wrong (only skimming ...) but that's looks like a known issue, unrelated to Qt - it's been previously discussed on the devel list and the forum, it's related to James' HDPI work for which he raised the required OSG version - to learn more, run a corresponding forum search: search.php?st=0&sk=t&sd=d&sr=posts&keywords=HDPI

For the background/explanation and "solution", see daveculp's original topic here (note that Dave is in fact a former FlightGear core developer, and still ran into this): osg::GLExtensions has not been declared
Please don't send support requests by PM, instead post your questions on the forum so that all users can contribute and benefit
Thanks & all the best,
Hooray
Help write next month's newsletter !
pui2canvas | MapStructure | Canvas Development | Programming resources
Hooray
 
Posts: 11117
Joined: Tue Mar 25, 2008 8:40 am

Re: Flightgear source code terminates in GLExtension.cpp

Postby wkitty42 » Wed Sep 05, 2018 9:09 pm

good find, Hooray! i remember reading that topic but it didn't affect me so i didn't make a point of retaining the details... i knew that "GLExtensions" was familiar to me but not why it was... now i know it was that topic...
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 4641
Joined: Fri Feb 20, 2015 3:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 14.04.5

Re: Flightgear source code terminates in GLExtension.cpp

Postby sathish » Tue Sep 11, 2018 10:04 am

wkitty42 wrote in Wed Sep 05, 2018 9:09 pm:good find, Hooray! i remember reading that topic but it didn't affect me so i didn't make a point of retaining the details... i knew that "GLExtensions" was familiar to me but not why it was... now i know it was that topic...


which topic u mean in the above quote
sathish
 
Posts: 16
Joined: Tue Mar 13, 2018 12:51 pm

Re: Flightgear source code terminates in GLExtension.cpp

Postby wkitty42 » Tue Sep 11, 2018 1:58 pm

the one that Hooray linked in the second paragraph... the link with "GLExtensions" in it...
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 4641
Joined: Fri Feb 20, 2015 3:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 14.04.5

Re: Flightgear source code terminates in GLExtension.cpp

Postby Hooray » Sat Sep 15, 2018 4:09 pm

The thing to keep in mind here is that the issue is unrelated to Qt/QQ2 - it's because of the HiDPI changes that end up using newer OSG functionality that may not yet available - I haven't build fgfs in months, so my info may be outdated here - however, last I checked, fgfs didn't complain about this during configuration/cmake time, so that the issue would only show up at build time - traditionally, fgfs devs have been rather conservative when it came up introducing additional/new dependencies, so I am not sure if got sorted meanwhile or not - but depending on the circumstances and the status quo, the "fix" might be as simple as raising the required osg version in CMakeLists.txt, alternatively wrapping those changes in #ifdefs and turn them into a cmake build option in the meantime. IMO, this would have been the proper fix, especially for people not even using any such functionality, who are still affected by this change.

If in doubt, report the issue using the issue tracker. Anyway, good luck.
Please don't send support requests by PM, instead post your questions on the forum so that all users can contribute and benefit
Thanks & all the best,
Hooray
Help write next month's newsletter !
pui2canvas | MapStructure | Canvas Development | Programming resources
Hooray
 
Posts: 11117
Joined: Tue Mar 25, 2008 8:40 am

Re: Flightgear source code terminates in GLExtension.cpp

Postby Hooray » Sun Sep 16, 2018 12:17 pm

wkitty42 wrote in Mon Sep 03, 2018 5:54 pm:disabling Qt may also affect the in-sim Aircraft Center... there are instructions somewhere (wiki?) on what to change in the sources to use the old Aircraft Center if it is desired in one's FG... it is only a coupld of lines, IIRC...


Yes, that's absolutely correct, even though I don't think I added those instructions to the wiki, but there should be a corresponding forum topic, it's a fairly simple change actually only involving a few lines of Nasal code.

As far as I know, the real issue however is that I don't think the package manager stuff received much/any testing by people not using Qt-enabled builds, so there may be plenty of issues that we are unaware of, because the original "Aircraft Center" simply got phased out when the Qt launcher got added.

Originally, the plans announced on the devel list/forum (respectively) stated that the new UI would use a common service layer back-end that could also be used by other front-ends, including Phi, but I am not sure how much of this ever materialized or not - quoting FlightGear core developer Torsten:

New Canvas GUI
Torsten wrote:There is currently heavy activity towards a new UI. There will be the HTML5 based version, I am currently working on and an internal implementation based on well supported libraries. Most likely, both will use a common service layer to provide necessary data.
Neither of those will use Nasal or Canvas to render the UI elements.

Torsten


In other words, I am not sure if it's even supposed to be possible to use a non-Qt enabled build (e.g. via Phi) to download/install and manage aircraft/scenery or not ?

Then again, technically there is really no reason why the same back-end could not be exposed via a CLI (Command Line Interface) so that non-Qt5 builds/users can still make use of the package manager back-end, especially if everything works through fgcommands - besides, this could be a great asset from a troubleshooting standpoint, i.e. people could run all sorts of tests in a scripted fashion to see if their aircraft can be easily downloaded/installed and configured, without requiring an interactive UI.

This could work analogous to the package manager on any modern Linux distro.

EDIT: The instructions on re-enabling the original Nasal/Canvas based Aircraft Center are to be found here: Subject: Reinstating Canvas based Aircraft Center for non Qt builds
Please don't send support requests by PM, instead post your questions on the forum so that all users can contribute and benefit
Thanks & all the best,
Hooray
Help write next month's newsletter !
pui2canvas | MapStructure | Canvas Development | Programming resources
Hooray
 
Posts: 11117
Joined: Tue Mar 25, 2008 8:40 am

Next

Return to Compiling

Who is online

Users browsing this forum: abassign and 0 guests