VS Code templates for dev & debug on native environments (nvidia-holo…

…scan#450) * Building & Debugging Holoscan applications natively Signed-off-by: Victor Chang <vicchang@nvidia.com> * Consolidate debugging tutorials Signed-off-by: Victor Chang <vicchang@nvidia.com> * Update per feedback Signed-off-by: Victor Chang <vicchang@nvidia.com> --------- Signed-off-by: Victor Chang <vicchang@nvidia.com> Signed-off-by: Rony Rado <rrado@nvidia.com>
ronyrad · Aug 15, 2024 · 2f2ef5b · 2f2ef5b
1 parent 6ab81c9
commit 2f2ef5b
Show file tree

Hide file tree

Showing 45 changed files with 621 additions and 4 deletions.
diff --git a/applications/nvidia_nim/nvidia_nim_imaging/README.md b/applications/nvidia_nim/nvidia_nim_imaging/README.md
@@ -46,10 +46,10 @@ In this section, we will show how to view the sample data and segmentation resul
    ```
 3. Locate the sample data volume and the segmentation results in `build/nvidia_nim_imaging/applications/nvidia_nim/nvidia_nim_imaging`
    ```
-   drwxr-xr-x 3 vicchang domain-users     4096 Jul  3 11:41 ./
-   drwxr-xr-x 4 vicchang domain-users     4096 Jul  3 11:40 ../
-   -rw-r--r-- 1 vicchang vicchang     27263336 Jul 23 14:22 example-1_seg.nrrd
-   -rw-r--r-- 1 vicchang vicchang     33037057 Jul 23 14:21 sample.nii.gz
+   drwxr-xr-x 3 user domain-users     4096 Jul  3 11:41 ./
+   drwxr-xr-x 4 user domain-users     4096 Jul  3 11:40 ../
+   -rw-r--r-- 1 user user         27263336 Jul 23 14:22 example-1_seg.nrrd
+   -rw-r--r-- 1 user user         33037057 Jul 23 14:21 sample.nii.gz
    ```
 5. In 3D Slicer, click *File*, *Add Data* and click *Choose File(s) to Add*.
    From the *Add Data into the scene* dialog, find and add the `sample.nii.gz` file and the `example-1_seg.nrrd` file.

diff --git a/tutorials/debugging/README.md b/tutorials/debugging/README.md
@@ -0,0 +1,8 @@
+# Debugging Holoscan & Holohub Applications
+
+Below is a collection of tutorials and templates designed for debugging Holoscan and Holohub applications:
+
+- [Debugging Holoscan Applications using VS Code](./vscode-native) - Learn how to develop and debug Holoscan applications natively using Visual Studio Code.
+- [Interactively Debugging a Holoscan Application](./cli_debugging) - Learn how to debug Holoscan applications using `gdb` and `pdb`.
+- [Holohub Dev Container](../../.devcontainer/) - Explore developing Holohub applications using VS Code and Dev Container.
+- [Debugging Holoscan Applications using Holoscan Container and Dev Container](./holoscan_container_vscode) - Develop Holoscan application using the Holoscan NGC Container inside VS Code Dev Container.
diff --git a/tutorials/cli_debugging/.gitignore → tutorials/debugging/cli_debugging/.gitignore b/tutorials/cli_debugging/.gitignore → tutorials/debugging/cli_debugging/.gitignore
diff --git a/tutorials/cli_debugging/Dockerfile → tutorials/debugging/cli_debugging/Dockerfile b/tutorials/cli_debugging/Dockerfile → tutorials/debugging/cli_debugging/Dockerfile
diff --git a/tutorials/cli_debugging/README.md → tutorials/debugging/cli_debugging/README.md b/tutorials/cli_debugging/README.md → tutorials/debugging/cli_debugging/README.md
diff --git a/tutorials/cli_debugging/debug_gdb.sh → ...ials/debugging/cli_debugging/debug_gdb.sh b/tutorials/cli_debugging/debug_gdb.sh → ...ials/debugging/cli_debugging/debug_gdb.sh
diff --git a/tutorials/cli_debugging/debug_legacy.sh → ...s/debugging/cli_debugging/debug_legacy.sh b/tutorials/cli_debugging/debug_legacy.sh → ...s/debugging/cli_debugging/debug_legacy.sh
diff --git a/tutorials/cli_debugging/debug_pdb.sh → ...ials/debugging/cli_debugging/debug_pdb.sh b/tutorials/cli_debugging/debug_pdb.sh → ...ials/debugging/cli_debugging/debug_pdb.sh
diff --git a/...li_debugging/holoscan_sdk_20240723_1.diff → ...li_debugging/holoscan_sdk_20240723_1.diff b/...li_debugging/holoscan_sdk_20240723_1.diff → ...li_debugging/holoscan_sdk_20240723_1.diff
diff --git a/tutorials/cli_debugging/metadata.json → ...als/debugging/cli_debugging/metadata.json b/tutorials/cli_debugging/metadata.json → ...als/debugging/cli_debugging/metadata.json
diff --git a/...container_vscode/.devcontainer/Dockerfile → ...container_vscode/.devcontainer/Dockerfile b/...container_vscode/.devcontainer/Dockerfile → ...container_vscode/.devcontainer/Dockerfile
diff --git a/...er_vscode/.devcontainer/devcontainer.json → ...er_vscode/.devcontainer/devcontainer.json b/...er_vscode/.devcontainer/devcontainer.json → ...er_vscode/.devcontainer/devcontainer.json
diff --git a/...scode/.devcontainer/initialize-command.sh → ...scode/.devcontainer/initialize-command.sh b/...scode/.devcontainer/initialize-command.sh → ...scode/.devcontainer/initialize-command.sh
diff --git a/...scode/.devcontainer/post-start-command.sh → ...scode/.devcontainer/post-start-command.sh b/...scode/.devcontainer/post-start-command.sh → ...scode/.devcontainer/post-start-command.sh
diff --git a/...ials/holoscan_container_vscode/.gitignore → ...ging/holoscan_container_vscode/.gitignore b/...ials/holoscan_container_vscode/.gitignore → ...ging/holoscan_container_vscode/.gitignore
diff --git a/...rials/holoscan_container_vscode/README.md → ...gging/holoscan_container_vscode/README.md b/...rials/holoscan_container_vscode/README.md → ...gging/holoscan_container_vscode/README.md
diff --git a/...s/holoscan_container_vscode/metadata.json → ...g/holoscan_container_vscode/metadata.json b/...s/holoscan_container_vscode/metadata.json → ...g/holoscan_container_vscode/metadata.json
diff --git a/...s/holoscan_container_vscode/src/README.md → ...g/holoscan_container_vscode/src/README.md b/...s/holoscan_container_vscode/src/README.md → ...g/holoscan_container_vscode/src/README.md
diff --git a/...ainer_vscode/static/vscode-breakpoint.png → ...ainer_vscode/static/vscode-breakpoint.png b/...ainer_vscode/static/vscode-breakpoint.png → ...ainer_vscode/static/vscode-breakpoint.png
diff --git a/...ntainer_vscode/static/vscode-explorer.png → ...ntainer_vscode/static/vscode-explorer.png b/...ntainer_vscode/static/vscode-explorer.png → ...ntainer_vscode/static/vscode-explorer.png
diff --git a/...r_vscode/static/vscode-missing-cppdbg.png → ...r_vscode/static/vscode-missing-cppdbg.png b/...r_vscode/static/vscode-missing-cppdbg.png → ...r_vscode/static/vscode-missing-cppdbg.png
diff --git a/...er_vscode/static/vscode-run-and-debug.png → ...er_vscode/static/vscode-run-and-debug.png b/...er_vscode/static/vscode-run-and-debug.png → ...er_vscode/static/vscode-run-and-debug.png
diff --git a/tutorials/debugging/vscode-native/.gitignore b/tutorials/debugging/vscode-native/.gitignore
@@ -0,0 +1 @@
+build/
diff --git a/tutorials/debugging/vscode-native/README.md b/tutorials/debugging/vscode-native/README.md
@@ -0,0 +1,272 @@
+# Develop and Debugging Holoscan Application Natively
+
+This tutorial will guide you through the steps to set up your development environment for building and debugging your applications using Holoscan SDK natively with VS Code.
+
+Whether you are a C++ or Python developer, you can use the tutorial as a reference to set up your development environment and debug your Holoscan application.
+
+> 💡 Note: This guide is specific to the Linux development environment and is tested on Ubuntu 22.04 LTS.
+
+## Prerequisites
+
+- [Holoscan SDK Prerequisites](https://docs.nvidia.com/holoscan/sdk-user-guide/sdk_installation.html#prerequisites)
+- [Visual Studio Code](https://code.visualstudio.com/)
+- [Holohub](https://github.com/nvidia-holoscan/holohub/)
+  ```bash
+  # clone the Holohub repository
+  git clone https://github.com/nvidia-holoscan/holohub.git
+  ```
+
+### C++ Prerequisites
+
+To build and debug your C++ applications natively, we must first install the redistribution of the Holoscan SDK. To install Holoscan SDK using a Debian package, refer to the Debian package installation section in the [Holoscan SDK documentation](https://docs.nvidia.com/holoscan/sdk-user-guide/sdk_installation.html#instructions).
+
+- [CMake Tools](https://marketplace.visualstudio.com/items?itemName=ms-vscode.cmake-tools) extension for VS Code
+- [CMake](https://cmake.org/cmake/help/latest/command/install.html) 3.24.0 or higher
+- Ninja 1.10 or higher
+  ```bash
+  sudo apt update && sudo apt install ninja-build
+  ```
+- gcc 11.4 or higher
+  ```bash
+  sudo apt update && sudo apt install build-essential
+  ```
+
+### Python Prerequisites
+
+- [Python C++ Debugger](https://marketplace.visualstudio.com/items?itemName=benjamin-simmonds.pythoncpp-debug) extension for VS Code
+- [Python 3.10](https://www.python.org/) or higher
+- [Holoscan SDK PyPI Wheel](https://pypi.org/project/holoscan/)
+  ```bash
+  pip install holoscan
+  ```
+- (Optional) Python virtual environment of your choice
+
+## Environment Setup
+
+In this section, we walk through setting up a development environment using VS Code with some templates that we have included in this directory. A Hello World Holoscan application in C++ and Python is also included in the `cpp/` and the `python/`, respectively.
+
+### C++
+
+The C++ example in this tutorial is pre-configured using the [CMake Tools](https://marketplace.visualstudio.com/items?itemName=ms-vscode.cmake-tools) extension in VS Code with a [CMake Preset](https://cmake.org/cmake/help/latest/manual/cmake-presets.7.html) file ([CMakePresets.json](cpp/CMakePresets.json)). Once installed, VS Code should include all the CMake options in the status bar, as shown below.
+
+<figure>
+ <img src="static/vscode-cmake-statusbar.png" alt="VS Code Status Bar" />
+ <figcaption>Figure 1: VS Code status bar with CMake options.</figcaption>
+</figure>
+
+
+Let's start a new instance of VS Code; run the following command from the root directory of the Holohub repository:
+
+```bash
+code tutorials/debugging/vscode-native/cpp
+```
+
+A new instance of VS Code shall open and display the following files in the **Explorer** tab.
+
+<figure>
+ <img src="static/vscode-cpp-files.png" alt="VS Code Hello World C++" />
+ <figcaption>Figure 2: VS Code Explorer showing files in the C++ Hello World sample application.</figcaption>
+</figure>
+
+#### Debugging
+
+The first time VS Code opens this directory, it may do one of the following actions depending on the version of VS Code and the CMake Tools extension installed:
+
+1. Prompt you to select a preset, **Debug** or **Release**. Select **Debug** to continue. This action configures CMake which creates a `build/` directory. Or,
+2. Automatically configures CMake with the **Debug** configure preset and creates a `build/` directory for you.
+
+If neither of these actions were performed, open the **Command Palette** from the **View** menu, or `Ctrl+Shift+P`. Select **CMake: Select Configure Preset** from the list of options and then select **Debug**. This configures CMake to build the Hello World sample application in debug mode using _g++_ as the compiler and _ninja_ as the build tool.
+
+Next, open the **Command Palette** again, and select **CMake: Build** and then select **build** from **Select a build task** dropdown.
+This action builds the Hello World binary and stores the artifact in `build/debug/src/hello_world`.
+
+Let's debug the Hello World application, open the [hello_world.cpp](cpp/src/hello_world.cpp#L55) file in VS Code, and set a breakpoint in the `main()` function. Switch to the **Run and Debug** tab in VS Code. Select **(gdb) Launch Hello World** from the dropdown and click **Start Debugging** icon (play button ▶️) to start debugging. VS Code should stop at the breakpoint:
+
+<figure>
+ <img src="static/vscode-cpp-breakpoint.png" alt="VS Code Hello World C++ Breakpoint" />
+ <figcaption>Figure 3: VS Code hitting the breakpoint set in the C++ Hello World sample application.</figcaption>
+</figure>
+
+##### Step into Holoscan Source Code
+
+To step into Holoscan SDK source code, we need to clone the Holoscan SDK and create a debug build of the Holoscan SDK. First, complete the steps described in the [Building Holoscan SDK](#building-holoscan-sdk) section and then follow these steps to configure your debugging environment:
+
+1. The Holoscan SDK build process creates an `install-[arch]/` directory upon completion. Open the [CMakePresets.json](cpp/CMakePresets.json#L19) and update the `HOLOSCAN_INSTALL_DIR` variable with the `install-[arch]` path. For example:
+
+   ```json
+   "cacheVariables": {
+      ...
+      "HOLOSCAN_INSTALL_DIR": "/home/user/holoscan-sdk/install-x86_64"
+   }
+   ```
+
+   > 💡 Tip: Step 3 of the [Building Holoscan SDK](#building-holoscan-sdk) section describes how to find the Holoscan SDK installation path.
+
+2. Open [launch.json](cpp/.vscode/launch.json#L22) and update the source map path **value** with the path to the `src/` directory of Holoscan SDK. For example:
+
+   ```json
+   "sourceFileMap": {
+        "/workspace/holoscan-sdk/src/": "/home/user/holoscan-sdk/src"
+    },
+   ```
+
+   > 💡 Tip: Change `/home/user/holoscan-sdk` to the path where you cloned the Holoscan SDK repository.
+
+3. Clean up the existing build directory by opening the **Command Palette** and select **CMake: Clean Rebuild** and select **build**.
+
+4. Add Holoscan SDK source code to the workspace: Select **Add Folder to Workspace...** from the **File** menu. Find and select the directory where Holoscan SDK repository resides. 
+   The **Explorer** should now look like this:
+   <figure>
+   <img src="static/vscode-cpp-holoscan-sdk.png" alt="VS Code C++ Workspace with Holoscan SDK" />
+   <figcaption>Figure 4: VS Code workspace with Holoscan SDK.</figcaption>
+   </figure>
+
+5. Open `src/core/application.cpp` from the `holoscan-sdk` folder. Find `void Application::run()` and set a breakpoint inside the function.
+
+6. Switch to the **Run and Debug** tab in VS Code. Select **(gdb) Launch Hello World** from the dropdown and click **Start Debugging** icon (play button ▶️) to start debugging. This time, VS Code should stop in the `main()` of Hello World and inside `void Application::run()`.
+
+#### Testing
+
+The C++ Hello World sample application includes a test case in the [CMakeLists.txt](./cpp/src/CMakeLists.txt#L31) file. To run this test case, ensure the **Test Preset** is set to `[Test All]` and then click the **Run CTest** button on the status bar. This action should run the test case and output the following:
+
+```bash
+[main] Building folder: /.../holohub/tutorials/debugging/vscode-native/cpp/build/debug
+[build] Starting build
+[proc] Executing command: /usr/local/bin/cmake --build /.../holohub/tutorials/debugging/vscode-native/cpp/build/debug --config Debug --target hello_world --
+[build] ninja: no work to do.
+[driver] Build completed: 00:00:00.027
+[build] Build finished with exit code 0
+[proc] Executing command: /usr/local/bin/ctest -T test --output-on-failure --output-on-failure --stop-on-failure -R ^EXAMPLE_CPP_HELLO_WORLD_TEST$
+[ctest]    Site: holoscan-dev
+[ctest]    Build name: Linux-g++
+[ctest] Test project /.../holohub/tutorials/debugging/vscode-native/cpp/build/debug
+[ctest]     Start 1: EXAMPLE_CPP_HELLO_WORLD_TEST
+[ctest] 1/1 Test #1: EXAMPLE_CPP_HELLO_WORLD_TEST .....   Passed    0.03 sec
+[ctest]
+[ctest] 100% tests passed, 0 tests failed out of 1
+[ctest]
+[ctest] Total Test time (real) =   0.03 sec
+[ctest] CTest finished with return code 0
+```
+
+### Python
+
+The Python example resides in `tutorials/debugging/vscode-native/python`. Open it with VS Code with the following command:
+
+```bash
+code tutorials/debugging/vscode-native/python
+```
+
+Inside VS Code, open the integrated terminal (select **Terminal** from the **View** menu) to set up a virtual environment and install the dependencies:
+
+```bash
+# Configure a Python virtual environment if desired, e.g.,
+python3 -m venv .venv
+
+# Install dependencies
+pip install -r ./requirements.txt
+```
+
+> 💡Tip: Install the Holoscan SDK PyPI package in your favorite Python virtual environment or select the **Python: Create Environment** command from the **Command Palette** to create a new virtual environment.
+
+#### Debugging
+
+Open the [hello_world.py](python/src/hello_world.py#L54) file and set a breakpoint in the `main()` function.
+
+A launch profile, **Python Debugger**, is configured in the [launch.json](python/.vscode/launch.json). Switch to the **Run and Debug** tab to select the launch profile from the list, then click the **Start Debugging** icon (play button ▶️) to run the application. VS Code should stop at your breakpoint:
+
+<figure>
+ <img src="static/vscode-python-breakpoint.png" alt="VS Code Hello World Python Breakpoint" />
+ <figcaption>Figure 5: VS Code hitting the breakpoint set in the Python Hello World sample application.</figcaption>
+</figure>
+
+##### Step into Holoscan Source Code
+
+To step into Holoscan SDK source code with a Python application, we need to clone the Holoscan SDK and create a debug build of the Holoscan SDK. Complete the steps described in the [Building Holoscan SDK](#building-holoscan-sdk) section and then follow these steps to configure your debugging environment:
+
+1. Open [launch.json](python/.vscode/launch.json#L22) and update `PYTHONPATH` and `LD_LIBRARY_PATH` environment variables with the path to the Holoscan SDK that we built in the previous step. For example:
+
+   ```json
+   "env": {
+        "PYTHONPATH": "/home/user/holoscan-sdk/install-x86-64/python/lib",
+        "LD_LIBRARY_PATH": "/home/user/holoscan-sdk/install-x86_64/lib"
+    },
+   ```
+   > 💡 Tip: Step 3 of the [Building Holoscan SDK](#building-holoscan-sdk) section describes how to find the Holoscan SDK installation path.
+
+2. Unlike the C++ debugger, VS Code does not support setting a `sourcemap`; therefore, we have to make a symbolic link to the `holoscan-sdk` directory that we just cloned:
+   ```bash
+   sudo mkdir /workspace
+   sudo ln -s /home/user/holoscan-sdk /workspace/holoscan-sdk
+   ```
+   > 💡 Tip: Change `/home/user/holoscan-sdk` to the path where you cloned the Holoscan SDK repository.
+
+3. Add Holoscan SDK source code to the workspace: Select **Add Folder to Workspace...** from the **File** menu. Find and select the directory where Holoscan SDK repository resides. 
+   The **Explorer** should now look like this:
+   <figure>
+   <img src="static/vscode-python-holoscan-sdk.png" alt="VS Code C++ Workspace with Holoscan SDK" />
+   <figcaption>Figure 6: VS Code workspace with Holoscan SDK.</figcaption>
+   </figure>
+
+4. Open `src/core/application.cpp` from the `holoscan-sdk` folder. Find `void Application::run()` and set a breakpoint inside the function.
+
+5. Switch to the **Run and Debug** tab in VS Code. Select **Python C++ Debugger** from the dropdown and click the **Start Debugging** icon (play button ▶️) to start debugging. This time, VS Code should stop in the `main()` function of the Hello World application and the `void Application::run()` function from Holoscan SDK.
+
+   > 💡 Tip: When the debug session starts, it stops at the top of the main application file and brings up a prompt in the terminal asking for superuser access.
+   > ```bash
+   > Superuser access is required to attach to a process. Attaching as superuser can potentially harm your computer. Do you want to continue? [y/N]
+   > ```
+   > You may answer `Y` or `y` to continue the debug session. The debugger shall now stop at the breakpoint you've set in the `application.cpp` file.
+
+#### Testing
+
+The Python Hello World sample application includes a test case in the [tests/](python/tests/) directory. To run the test case, ensure you have all the requirements installed from the previous [step](#python), and then run the following command:
+
+```bash
+$ pytest -v
+
+========================================================================================== test session starts ==========================================================================================
+platform linux -- Python 3.10.12, pytest-8.3.2, pluggy-1.5.0 -- /home/user/holohub/tutorials/debugging/vscode-native/python/.venv/bin/python
+cachedir: .pytest_cache
+rootdir: /home/user/holohub/tutorials/debugging/vscode-native/python
+configfile: pytest.ini
+collected 1 item
+
+test_hello_world.py::test_hello_world PASSED [100%]
+
+=========================================================================================== 1 passed in 0.03s ===========================================================================================
+
+```
+
+## Building Holoscan SDK
+
+If you plan to step into the Holoscan SDK source code when debugging your application, you must build the Holoscan SDK from the source. To do this, follow these steps:
+
+1. Clone Holoscan SDK:
+
+   ```bash
+   git clone --depth 1 --branch <tag> https://github.com/nvidia-holoscan/holoscan-sdk.git
+
+   # For eaxmple, to clone and checkout Holoscan version 2.2.0
+   git clone --depth 1 --branch v2.2.0 https://github.com/nvidia-holoscan/holoscan-sdk.git
+   ```
+
+   > 🔗 Link: [Holoscan SDK tags](https://github.com/nvidia-holoscan/holoscan-sdk/tags)
+
+2. Build the Holoscan SDK in Debug mode:
+
+   ```bash
+   cd holoscan-sdk
+   ./run build --type debug
+   ```
+
+   > 💡 Tip: A comprehensive guide on how to build the Holoscan SDK is also available from the [Holoscan SDK](https://github.com/nvidia-holoscan/holoscan-sdk/blob/v2.2.0/DEVELOP.md#building-the-sdk-from-source) repository.
+
+   > 💡 Tip: To build Holoscan SDK v2.2.0 or earlier, check this [Github issue](https://github.com/nvidia-holoscan/holoscan-sdk/issues/30) for additional steps.
+
+3. Run the following command to find the Holoscan SDK installation path, we will use it later:
+   ```bash
+   find $PWD -name "install-*" -type d
+   # example output
+   /home/user/holoscan-sdk/install-x86_64
+   ```
diff --git a/tutorials/debugging/vscode-native/cpp/.gitignore b/tutorials/debugging/vscode-native/cpp/.gitignore
@@ -0,0 +1 @@
+build/
diff --git a/tutorials/debugging/vscode-native/cpp/.vscode/launch.json b/tutorials/debugging/vscode-native/cpp/.vscode/launch.json
@@ -0,0 +1,35 @@
+{
+    // Use IntelliSense to learn about possible attributes.
+    // Hover to view descriptions of existing attributes.
+    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
+    "version": "0.2.0",
+    "configurations": [
+        {
+            "name": "(gdb) Launch Hello World",
+            "type": "cppdbg",
+            "request": "launch",
+            "program": "${command:cmake.buildDirectory}/src/hello_world",
+            "args": [],
+            "stopAtEntry": false,
+            "cwd": "${command:cmake.buildDirectory}",
+            "environment": [
+                {
+                    "name": "HOLOSCAN_LOG_LEVEL",
+                    "value": "DEBUG"
+                }
+            ],
+            "sourceFileMap": {
+                "/workspace/holoscan-sdk/src/": "/home/user/holoscan-sdk/src"
+            },
+            "externalConsole": false,
+            "MIMode": "gdb",
+            "setupCommands": [
+                {
+                    "description": "Enable pretty-printing for gdb",
+                    "text": "-enable-pretty-printing",
+                    "ignoreFailures": true
+                }
+            ]
+        }
+    ]
+}
diff --git a/tutorials/debugging/vscode-native/cpp/.vscode/settings.json b/tutorials/debugging/vscode-native/cpp/.vscode/settings.json
@@ -0,0 +1,4 @@
+{
+    "cmake.options.statusBarVisibility": "visible",
+    "cmake.useCMakePresets": "always",
+}
diff --git a/tutorials/debugging/vscode-native/cpp/CMakeLists.txt b/tutorials/debugging/vscode-native/cpp/CMakeLists.txt
@@ -0,0 +1,21 @@
+# SPDX-FileCopyrightText: Copyright (c) 2024 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
+# SPDX-License-Identifier: Apache-2.0
+#
+# Licensed under the Apache License, Version 2.0 (the \"License\");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an \"AS IS\" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+cmake_minimum_required(VERSION 3.20)
+project(holoscan_hello_world LANGUAGES C CXX)
+
+include(CTest)
+
+add_subdirectory(src)