Differences between revisions 1 and 11 (spanning 10 versions)
Revision 1 as of 2009-06-30 16:21:17
Size: 1768
Editor: 84-75-191-209
Comment:
Revision 11 as of 2020-09-11 09:09:07
Size: 2276
Editor: bonaccos
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
#rev 2020-09-02 davidsch
#rev 2018-08-28 davidsch
Line 2: Line 5:
=== Compiling OpenGL applications on Debian Linux ===
The Debian platform managed by the ISG.EE has a new directory layout for the OpenGL libraries and headers:
Line 5: Line 6:
Libraries: === Compiling OpenGL/ NVidia CUDA-based applications on Debian Linux ===
The Debian platform managed by ISG.EE uses the following directory layout for the OpenGL libraries and headers:
Line 7: Line 9:
{{{
The /usr/!X11R6/lib/libGL* libraries are symbolic links to the hardware-specific libraries. There is a mechanism in the starup process of each client workstation which detects the accurate OpenGL library based on the information about the graphics card and the kernel driver.
==== Libraries ====

 * The /usr/lib/x86_64-linux-gnu/libGL*.so OpenGL libraries are symbolic links to the hardware-specific libraries. There is a mechanism in the starup process of each client workstation which detects the accurate OpenGL library based on the information about the graphics card and the kernel driver. The CUDA runtime libraries are found in the same directory.

==== Header Files ====
 * The OpenGL headers are found under /usr/include/GL. For NVidia programming, a CUDA toolkit that should work with the installed NVidia graphics card is installed (CUDA headers in /usr/include).

==== Compiling sources and linking against NVidia libraries ====

 * No special CFLAGS/ CXXFLAGS and LDFLAGS must be set. The required headers and libraries are all found under the standard system paths. If you use an own OpenGL/ CUDA toolkit, e.g. installed in your home, make sure it is compatible with the graphics driver/ hardware installed on the system. Note: if you don't have brand new hardware in your computer, the most current CUDA release most probably won't work with it - use an older relase or ask ISG.EE if you are in doubt about the right version.
 * Then set CFLAGS (for C-compiler), CXXFLAGS (for C++ compiler) and LDFLAGS (linker flags) as follows: {{{

Assume you have installed the toolkit under /home/$USER/toolkit, then set the mentioned environment variables
in your Debian shell (bash, tcsh, ...) as follows, before you start compiling/ linking:

export CFLAGS="-I/home/$USER/toolkit/include"
export CXXFLAGS="$CFLAGS"
export LDFLAGS="-L/home/$USER/toolkit/lib -Wl,-rpath,/home/$USER/toolkit/lib"

$USER must of course be replaced with your ETH (login-) username.
Line 10: Line 30:
Header Files:
Line 12: Line 31:
{{{
1. For compatibility reasons, the default OpenGL headers (from the MESA package) are saved in their default location, i.e. /usr/X11R6/include/GL which points to the same directory as /usr/include/GL.
2. The extended OpenGL header files from Nvidia are stored in /usr/lib/nvidia/include/GL which have to be included in the compile path in order to use the extended Nvidia functions.
}}}
Compiling sources and linking against the NVidia libraries:
==== Reccomendation ====
Line 18: Line 33:
{{{
add to CFLAGS / CPPFLAGS / CXXFLAGS
`-I/usr/lib/nvidia/include/GL`
add to LDFLAGS ``
`-L/usr/lib/nvidia/lib` ` -Wl,-rpath -Wl,/usr/lib/nvidia/lib`
}}}
Remarks:
That said we encourage the use of CUDA Toolkit within Conda environments. More details can be found in the [[Programming/Languages/GPUCPU|Working with GPU or CPU in data sciences]] and [[Programming/Languages/Conda|Conda]] subpages of this wiki.
Line 26: Line 35:
{{{
If you are using the libGLU you will get the following linker warning: `/usr/bin/ld: warning: libstdc++.so.5, needed by /usr/bin/../lib/libGLU.so, may conflict with libstdc++.so.6`
This shouldn't affect your programs (the libGLU was linked against the old C++ standard library and most of the installed gnu compilers will link against the newer library).
If you have problems linking against `libGL.so` from `/usr/lib` it is possible to access symbols directly from the NVidia opengl library in `/usr/lib/nvidia/lib`:
remove `-L/usr/lib` and add instead `-L/usr/lib/nvidia/lib -lGL` to your `LDFLAGS` environment/ make variable.
}}}
----
[[CategoryLXSW]]

OpenGL

Compiling OpenGL/ NVidia CUDA-based applications on Debian Linux

The Debian platform managed by ISG.EE uses the following directory layout for the OpenGL libraries and headers:

Libraries

  • The /usr/lib/x86_64-linux-gnu/libGL*.so OpenGL libraries are symbolic links to the hardware-specific libraries. There is a mechanism in the starup process of each client workstation which detects the accurate OpenGL library based on the information about the graphics card and the kernel driver. The CUDA runtime libraries are found in the same directory.

Header Files

  • The OpenGL headers are found under /usr/include/GL. For NVidia programming, a CUDA toolkit that should work with the installed NVidia graphics card is installed (CUDA headers in /usr/include).

Compiling sources and linking against NVidia libraries

  • No special CFLAGS/ CXXFLAGS and LDFLAGS must be set. The required headers and libraries are all found under the standard system paths. If you use an own OpenGL/ CUDA toolkit, e.g. installed in your home, make sure it is compatible with the graphics driver/ hardware installed on the system. Note: if you don't have brand new hardware in your computer, the most current CUDA release most probably won't work with it - use an older relase or ask ISG.EE if you are in doubt about the right version.
  • Then set CFLAGS (for C-compiler), CXXFLAGS (for C++ compiler) and LDFLAGS (linker flags) as follows:

    Assume you have installed the toolkit under /home/$USER/toolkit, then set the mentioned environment variables
    in your Debian shell (bash, tcsh, ...) as follows, before you start compiling/ linking:
    
    export CFLAGS="-I/home/$USER/toolkit/include"
    export CXXFLAGS="$CFLAGS"
    export LDFLAGS="-L/home/$USER/toolkit/lib -Wl,-rpath,/home/$USER/toolkit/lib"
    
    $USER must of course be replaced with your ETH (login-) username.

Reccomendation

That said we encourage the use of CUDA Toolkit within Conda environments. More details can be found in the Working with GPU or CPU in data sciences and Conda subpages of this wiki.


CategoryLXSW

Programming/Libraries/OpenGL (last edited 2023-10-16 13:36:41 by alders)