OpenGL vs. OpenGL/ES

It looks like my test code is linked against OpenGL/ES (rosmake indigo).
I do need full OpenGL functionality, e.g. QGLViewer with polygons.
Is there an easy way to change the library linked?

I am unfamiliar with the particular software, but if something was linked against OpenGLES, then it would have to be ported to OpenGL before linkage could be changed. OpenGL and OpenGLES are closely related, but I have no idea how difficult porting would be…quite often if you port something then you will suddenly find other libraries linked to the original library break, and thus a chain of porting from OpenGLES to OpenGL would be required (such a project suddenly goes up exponentially in required effort).

The source code was running perfectly under OpenGL on an Intel Linux box (no Tegra).
The code should be working with OpenGL, but functions like polygons just get ignored when running under OpenGL/ES.
Compiling and linking the same source code works in both OpenGL flavors, but in OpenGL/ES nothing gets drawn.

I do not know about that software, but is there a URL available for test compiling?

If the software is designed for OpenGL, then it should not be trying to link as OpenGLES unless there is some sort of configuration stage and someone wrote the configuration scripts to also work with OpenGLES. If the software is popular enough then perhaps the software had options for both OpenGL and OpenGLES…in that case the platform would have to have a default of which to choose or else the configuration script would have options to force which to choose.

The software is on GitHub:
To compile you’d also need ROS Indigo.
I’m very keen to run this on the TX1, then then use the GPU as much as possible for max speed.
My suspicion is that the QGLViewer library provided in JetPack was compiled with GLES.

You can run the "ldd " command and see what other files it is linked to. Do you know which library file provides QGLViewer? Probably something in “/usr/lib/arm-linux-gnueabihf/” (symbols are stripped on most of those so ldd works but you can’t look for individual symbols with nm…if you happen to know which file provides the symbol though you’re in luck).

Here’s what I get from
ubuntu@tegra-ubuntu:/usr/lib/arm-linux-gnueabihf$ ldd => (0xf7037000) => /usr/lib/arm-linux-gnueabihf/tegra-egl/ (0xf6f90000) => /usr/lib/arm-linux-gnueabihf/ (0xf6f5c000) => /usr/lib/arm-linux-gnueabihf/ (0xf6ef4000) => /usr/lib/arm-linux-gnueabihf/ (0xf6835000) => /usr/lib/arm-linux-gnueabihf/ (0xf6629000) => /usr/lib/arm-linux-gnueabihf/ (0xf657e000) => /lib/arm-linux-gnueabihf/ (0xf6512000) => /lib/arm-linux-gnueabihf/ (0xf64f1000) => /lib/arm-linux-gnueabihf/ (0xf640a000) => /lib/arm-linux-gnueabihf/ (0xf63ef000) => /lib/arm-linux-gnueabihf/ (0xf63e3000) => /usr/lib/arm-linux-gnueabihf/tegra/ (0xf63c8000)
/lib/ (0xab0aa000) => /usr/lib/arm-linux-gnueabihf/ (0xf6347000) => /usr/lib/arm-linux-gnueabihf/ (0xf6261000) => /usr/lib/arm-linux-gnueabihf/ (0xf6232000) => /usr/lib/arm-linux-gnueabihf/ (0xf621a000) => /lib/arm-linux-gnueabihf/ (0xf6152000) => /lib/arm-linux-gnueabihf/ (0xf6132000) => /lib/arm-linux-gnueabihf/ (0xf6117000) => /usr/lib/arm-linux-gnueabihf/ (0xf60b0000) => /usr/lib/arm-linux-gnueabihf/ (0xf6072000) => /usr/lib/arm-linux-gnueabihf/ (0xf6064000) => /usr/lib/arm-linux-gnueabihf/ (0xf604b000) => /usr/lib/arm-linux-gnueabihf/ (0xf6039000) => /usr/lib/arm-linux-gnueabihf/ (0xf602a000) => /usr/lib/arm-linux-gnueabihf/ (0xf6017000) => /lib/arm-linux-gnueabihf/ (0xf6009000) => /usr/lib/arm-linux-gnueabihf/tegra/ (0xf5ff2000) => /usr/lib/arm-linux-gnueabihf/tegra/ (0xf5f8d000) => /usr/lib/arm-linux-gnueabihf/ (0xf5f72000) => /lib/arm-linux-gnueabihf/ (0xf5f52000) => /usr/lib/arm-linux-gnueabihf/ (0xf5f11000) => /usr/lib/arm-linux-gnueabihf/ (0xf5f06000) => /lib/arm-linux-gnueabihf/ (0xf5ece000) => /usr/lib/arm-linux-gnueabihf/ (0xf5ebf000) => /lib/arm-linux-gnueabihf/ (0xf5eb3000) => /usr/lib/arm-linux-gnueabihf/tegra/ (0xf5ea0000) => /usr/lib/arm-linux-gnueabihf/ (0xf5e94000) => /usr/lib/arm-linux-gnueabihf/tegra/ (0xf5e7b000)

And here’s the app I’m running. is by defualt (JetPack) linked to the libGLES library.

ubuntu@tegra-ubuntu:~/rosbuild_ws/package_dir/lsd_slam/lsd_slam_viewer$ ldd bin/viewer => (0xf7173000) => /opt/ros/indigo/lib/ (0xf7162000) => /opt/ros/indigo/lib/ (0xf714e000) => /opt/ros/indigo/lib/ (0xf7116000) => /opt/ros/indigo/lib/ (0xf7020000) => /lib/arm-linux-gnueabihf/ (0xf6fe2000) => /opt/ros/indigo/lib/ (0xf6fbc000) => /opt/ros/indigo/lib/ (0xf6fb1000) => /opt/ros/indigo/lib/ (0xf6f8b000) => /opt/ros/indigo/lib/ (0xf6f7d000) => /usr/lib/arm-linux-gnueabihf/ (0xf6f72000) => /usr/lib/arm-linux-gnueabihf/ (0xf6f59000) => /usr/lib/arm-linux-gnueabihf/ (0xf6ef1000) => /usr/lib/arm-linux-gnueabihf/ (0xf6832000) => /usr/lib/arm-linux-gnueabihf/ (0xf6626000) => /usr/lib/arm-linux-gnueabihf/ (0xf65b7000) => /usr/lib/arm-linux-gnueabihf/ (0xf6567000) => /usr/lib/arm-linux-gnueabihf/ (0xf651e000) => /usr/lib/arm-linux-gnueabihf/ (0xf6474000) => /lib/arm-linux-gnueabihf/ (0xf6408000) => /lib/arm-linux-gnueabihf/ (0xf63e7000) => /lib/arm-linux-gnueabihf/ (0xf62ff000)
/lib/ (0xab00d000) => /opt/ros/indigo/lib/ (0xf62ca000) => /usr/lib/arm-linux-gnueabihf/ (0xf62bb000) => /opt/ros/indigo/lib/ (0xf62af000) => /lib/arm-linux-gnueabihf/ (0xf629b000) => /opt/ros/indigo/lib/ (0xf627d000) => /usr/lib/arm-linux-gnueabihf/ (0xf6265000) => /opt/ros/indigo/lib/ (0xf6250000) => /opt/ros/indigo/lib/ (0xf6246000) => /usr/lib/ (0xf610f000) => /usr/lib/arm-linux-gnueabihf/ (0xf605f000) => /lib/arm-linux-gnueabihf/ (0xf6051000) => /usr/lib/arm-linux-gnueabihf/ (0xf5fd0000) => /usr/lib/arm-linux-gnueabihf/tegra-egl/ (0xf5fbf000) => /usr/lib/arm-linux-gnueabihf/ (0xf5ed9000) => /usr/lib/arm-linux-gnueabihf/ (0xf5ea9000) => /usr/lib/arm-linux-gnueabihf/ (0xf5e92000) => /lib/arm-linux-gnueabihf/ (0xf5dca000) => /lib/arm-linux-gnueabihf/ (0xf5daa000) => /lib/arm-linux-gnueabihf/ (0xf5d8f000) => /usr/lib/arm-linux-gnueabihf/ (0xf5d27000) => /usr/lib/arm-linux-gnueabihf/ (0xf5cea000) => /usr/lib/arm-linux-gnueabihf/ (0xf5cdc000) => /usr/lib/arm-linux-gnueabihf/ (0xf5cc3000) => /usr/lib/arm-linux-gnueabihf/ (0xf5cb1000) => /usr/lib/arm-linux-gnueabihf/ (0xf5ca1000) => /usr/lib/arm-linux-gnueabihf/ (0xf5c8f000) => /lib/arm-linux-gnueabihf/ (0xf5c84000) => /usr/lib/arm-linux-gnueabihf/ (0xf5c50000) => /usr/lib/arm-linux-gnueabihf/ (0xf5c1e000) => /usr/lib/arm-linux-gnueabihf/ (0xf5c13000) => /usr/lib/arm-linux-gnueabihf/ (0xf5c07000) => /usr/lib/arm-linux-gnueabihf/ (0xf5bfd000) => /usr/lib/arm-linux-gnueabihf/ (0xf5be7000) => /usr/lib/arm-linux-gnueabihf/ (0xf5bdc000) => /usr/lib/arm-linux-gnueabihf/ (0xf5bd1000) => /usr/lib/arm-linux-gnueabihf/ (0xf5bc7000) => /usr/lib/arm-linux-gnueabihf/ (0xf5bbb000) => /usr/lib/arm-linux-gnueabihf/ (0xf5ba1000) => /usr/lib/arm-linux-gnueabihf/ (0xf5b97000) => /usr/lib/arm-linux-gnueabihf/ (0xf5b8a000) => /usr/lib/arm-linux-gnueabihf/ (0xf5b7a000) => /usr/lib/arm-linux-gnueabihf/ (0xf5b64000) => /usr/lib/arm-linux-gnueabihf/ (0xf5b10000) => /usr/lib/arm-linux-gnueabihf/ (0xf58b2000) => /usr/lib/arm-linux-gnueabihf/ (0xf58a2000) => /usr/lib/arm-linux-gnueabihf/ (0xf5881000) => /usr/lib/arm-linux-gnueabihf/ (0xf585d000) => /usr/lib/arm-linux-gnueabihf/ (0xf575f000) => /usr/lib/arm-linux-gnueabihf/ (0xf5609000) => /usr/lib/arm-linux-gnueabihf/tegra/ (0xf55a4000) => /usr/lib/arm-linux-gnueabihf/tegra/ (0xf5589000) => /usr/lib/arm-linux-gnueabihf/tegra/ (0xf5572000) => /lib/arm-linux-gnueabihf/ (0xf5552000) => /usr/lib/arm-linux-gnueabihf/ (0xf5511000) => /usr/lib/arm-linux-gnueabihf/ (0xf5505000) => /lib/arm-linux-gnueabihf/ (0xf54cd000) => /usr/lib/arm-linux-gnueabihf/ (0xf54bf000) => /lib/arm-linux-gnueabihf/ (0xf54b3000) => /usr/lib/arm-linux-gnueabihf/ (0xf54a6000) => /lib/arm-linux-gnueabihf/ (0xf549b000) => /lib/arm-linux-gnueabihf/ (0xf5464000) => /usr/lib/arm-linux-gnueabihf/ (0xf3df0000) => /usr/lib/arm-linux-gnueabihf/tegra/ (0xf3ddc000) => /usr/lib/arm-linux-gnueabihf/tegra/ (0xf3dc4000)

In the case where both GL and GLES are linked in, I would tend to think that it is possible to use either GL/GLES API so far as C/C++ code goes (basically using the correct header). Whether there is some other limitation, e.g., problems from mixing GL and GLES contexts, I do not know. If the JTX1 QGLViewer provides access only via GLES and QGLViewer on other platforms has a richer API set (GL versus GLES) I’m not sure if there is any kind of workaround.

Looks like QGLViewer came in via apt-get, so I’ll dig deeper how that is compiled.
Stay tuned…

Any ideas which of the following packages is present in JetPack already and shouldn’t be retrieved via apt-get?
liblapack-dev libblas-dev freeglut3-dev libqglviewer-qt4-dev libsuitesparse-dev libx11-dev

I’m unsure of the meaning of “shouldn’t”. Are you worried about conflict with the nVidia-specific files? If so, I doubt any of those would harm anything. You can run this command before and after a software install to validate if nVidia-specific files are still correct:

sha1sum -c /etc/nv_tegra_release

Thank you, that’s a useful one. In my system I got all OK, so now I need to find out how to configure QGLViewer.

Please help me out to solve this issue.
I am working on 3D software and while loading the data the error message arise as "The NVIDIA OPEN GL DRIVER LOST CONNECTION WITH THE DISPLAY DRIVER DUE TO EXCEEDING THE WINDOW TIME-OUT LIMIT AND IS UNABLE TO CONTINuE. Error code :7.
How can i solve this problem ? Where i need go and get this problem fix ?

Under Linux X11 the execution of an OpenGL app and its display can be on different machines. The first question would if you were running the app locally, or if you used a remote login? In the case of remote login, there is a strong chance that security or network settings got in the way. If using remote login, please describe the method of login and the host video hardware and o/s.