|
Size: 1748
Comment:
|
← Revision 17 as of 2023-10-16 13:36:41 ⇥
Size: 3300
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| #rev 2020-09-02 davidsch | |
| Line 4: | 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 7: | Line 6: |
| Libraries: | == Compiling OpenGL/ NVidia CUDA-based applications on Debian Linux == The Debian platform managed by ISG D-ITET uses the following directory layout for the OpenGL libraries and headers: |
| Line 9: | Line 9: |
| {{{ The /usr/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 startup 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. === OpenGL header files === The OpenGL headers are found under `/usr/include/GL`. === CUDA header files === For NVidia programming, a CUDA toolkit matching the installed NVidia driver is selected when a toolkit program like `nvcc`is run.<<BR>> Any CUDA headers have to bee included by manually matching the toolkit version used. Check the content of the SEPP package [[https://www.sepp.ee.ethz.ch/sepp-debian/cuda_toolkit-1x.x-sr.html|cuda_toolkit-1x.x-sr]] for available versions by listing its contents with `ls /usr/pack/cuda_toolkit-1x.x-sr` Usually, there is a lower driver/toolkit version combo for desktop PCs and a higher version combo for Slurm GPU nodes: * For desktop PCs: driver version `418` works with toolkit version `10.1.243` * For Slurm GPU nodes: driver version `470` works with toolkit version `11.4.4` The following environment variables have to be set with the correct driver or toolkit version: {{{#!highlight bash numbers=disable export CPPFLAGS='-I/usr/pack/cuda_toolkit-1x.x-sr/<driver or toolkit version>/include'` export LDFLAGS='-L/usr/pack/cuda_toolkit-1x.x-sr/<driver or toolkit version>/lib64 -Wl,-rpath,/usr/pack/cuda_toolkit-1x.x-sr/<driver or toolkit version>/lib64' ` |
| Line 12: | Line 28: |
| Header Files: | |
| Line 14: | Line 29: |
| {{{ 1. For compatibility reasons, the default OpenGL headers (from the MESA package) are saved in their default location, /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 NVidia libraries === * Make sure no special `CPPFLAGS` and `LDFLAGS` are set. The required headers and libraries are all found under the standard system paths. If you use your 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 D-ITET if you are in doubt about the right version. * Then set `CPPFLAGS` (for the C preprocessor used by most compilers) and `LDFLAGS` (linker flags) as follows: Assuming you installed the toolkit under `/home/$USER/toolkit` you set the mentioned environment variables in your Debian shell (`bash`, `tcsh`, ...) as follows, before you start compiling/ linking: {{{#!highlight bash numbers=disable export CPPFLAGS="-I/home/$USER/toolkit/include" export LDFLAGS="-L/home/$USER/toolkit/lib -Wl,-rpath,/home/$USER/toolkit/lib" |
| Line 18: | Line 38: |
| Compiling sources and linking against the NVidia libraries: | `$USER` must of course be replaced with your ETH (login-)username. |
| Line 20: | Line 40: |
| {{{ 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: |
=== Recomendation === 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 28: | Line 43: |
| {{{ 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. }}} |
OpenGL
Compiling OpenGL/ NVidia CUDA-based applications on Debian Linux
The Debian platform managed by ISG D-ITET 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 startup 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.
OpenGL header files
The OpenGL headers are found under /usr/include/GL.
CUDA header files
For NVidia programming, a CUDA toolkit matching the installed NVidia driver is selected when a toolkit program like nvccis run.
Any CUDA headers have to bee included by manually matching the toolkit version used. Check the content of the SEPP package cuda_toolkit-1x.x-sr for available versions by listing its contents with ls /usr/pack/cuda_toolkit-1x.x-sr
Usually, there is a lower driver/toolkit version combo for desktop PCs and a higher version combo for Slurm GPU nodes:
For desktop PCs: driver version 418 works with toolkit version 10.1.243
For Slurm GPU nodes: driver version 470 works with toolkit version 11.4.4
The following environment variables have to be set with the correct driver or toolkit version:
export CPPFLAGS='-I/usr/pack/cuda_toolkit-1x.x-sr/<driver or toolkit version>/include'`
export LDFLAGS='-L/usr/pack/cuda_toolkit-1x.x-sr/<driver or toolkit version>/lib64 -Wl,-rpath,/usr/pack/cuda_toolkit-1x.x-sr/<driver or toolkit version>/lib64' `
Compiling sources and linking against NVidia libraries
Make sure no special CPPFLAGS and LDFLAGS are set. The required headers and libraries are all found under the standard system paths. If you use your 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 D-ITET if you are in doubt about the right version.
Then set CPPFLAGS (for the C preprocessor used by most compilers) and LDFLAGS (linker flags) as follows:
Assuming you installed the toolkit under /home/$USER/toolkit you set the mentioned environment variables in your Debian shell (bash, tcsh, ...) as follows, before you start compiling/ linking:
export CPPFLAGS="-I/home/$USER/toolkit/include" export LDFLAGS="-L/home/$USER/toolkit/lib -Wl,-rpath,/home/$USER/toolkit/lib"
$USER must of course be replaced with your ETH (login-)username.
Recomendation
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.