Installing the NAP release involves extracting the archive and running our script to guide you through dependency installation. Projects reside within the framework folder structure, and as such we recommend extracting the release into a user directory instead of a system directory. The path to the nap root directory should not contain any white space characters.
The prerequisites installation script is called check_build_environment and can be found in the tools directory within the release. The script attempts to verify that your build environment is ready for NAP and is designed to be re-run until all checks are successfully passed.
NAP 0.8.0 supports Visual Studio 2019 & 2022 on Windows and make files on Linux. Instead of using these environments you can use Visual Studio Code or CLion to author your code. Although we don't officially support these environments others have confirmed that they work as expected. Both Visual Studio Code and CLion can be configured using CMake, which is the system NAP uses to build and package applications.
NAP 0.8.0 supports Windows 10 & 11 (x86_64) with Visual Studio 2019 or 2022.
Download and install Visual Studio 2022. This link points to the community edition which can be used for free. Make sure to select Desktop development with C++ when installing Visual Studio, including MSVC v143 - VS 2022 C++ x64/x86 and the Windows 10 SDK. Other settings are optional.
NAP-0.8.0-Win64-x86_64.zip using Explorer (or your preferred tool)NAP-0.8.0-Win64-x86_64\tools run check_build_environment.bat to guide you through installing prerequisites, following the instructionsNAP-0.8.0-Win64-x86_64\demos\helloworld in Explorerregenerate.batRelease configurationNAP 0.8.0 supports Ubuntu Linux 24.04 LTS on x86-64 machines using GCC. Although NAP is known to run on other distros: Ubuntu is currently the only supported Linux desktop environment.
Only the Raspberry Pi 4 & 5 running Raspbian bookworm (v12, arm64) is 'fully' supported. Headless applications and services without graphics should run on older models, although this has not been tested. Please note that although most demos work fine, we did run into minor render issues with the heightmap and computeflocking demos. Using a more recent (upstream) driver improved overall performance and resolved most known render issues.
When Wayland is configured as the display server, NAP applications will run in native wayland mode if the compositor supports wp_fifo_manager_v1; otherwise the system will revert back to XWayland for performance reasons. You can force applications to run in native wayland mode by selecting wayland as the Video Driver in the nap::RenderServiceConfiguration. Napkin is set up to always use XWayland for compatibility, but it can be run as a native Wayland application by setting the QT_QPA_PLATFORM environment variable to wayland.
check_build_environment script to guide you through installing prerequisites, following the instructions: check_build_environment after those changes have been made to verify the final environment