_            _    _        _         _
      /\ \         /\ \ /\ \     /\_\      / /\
      \_\ \       /  \ \\ \ \   / / /     / /  \
      /\__ \     / /\ \ \\ \ \_/ / /     / / /\ \__
     / /_ \ \   / / /\ \ \\ \___/ /     / / /\ \___\
    / / /\ \ \ / / /  \ \_\\ \ \_/      \ \ \ \/___/
   / / /  \/_// / /   / / / \ \ \        \ \ \
  / / /      / / /   / / /   \ \ \   _    \ \ \
 / / /      / / /___/ / /     \ \ \ /_/\__/ / /
/_/ /      / / /____\/ /       \ \_\\ \/___/ /
\_\/       \/_________/         \/_/ \_____\/
nvidia-cg-toolkit 3.1
Dependencies: gcc@14.3.0 glibc@2.41 glu@9.0.2 libice@1.1.2 libsm@1.2.5 libxmu@1.2.1 libxt@1.3.1 libxi@1.8.2 libxext@1.3.6 libx11@1.8.12
Channel: nonguix
Location: nongnu/packages/game-development.scm (nongnu packages game-development)
Home page: https://developer.nvidia.com/cg-toolkit
Licenses: Nonfree⚠
Build system: binary
Synopsis: High-level shading language
Description:

NVIDIA introduced programmable shading with Cg, which supported dozens of different OpenGL and DirectX profile targets. It allowed developers to incorporate interactive effects within 3D applications and share them among other Cg applications, across graphics APIs, and most operating systems as well as balance effect complexities with client GPU capabilities.

The Cg Toolkit is a legacy NVIDIA toolkit no longer under active development or support. It is not recommended using it in new development projects because future hardware features may not be supported. Going forward, new development should opt for GLSL rather than Cg.

Total packages: 1