group examples, build.sh

Author: stephen-derosa

CMakeLists.txt

@@ -62,11 +62,11 @@ add_subdirectory(basic_room)
 add_subdirectory(simple_room)
 add_subdirectory(simple_rpc)
 add_subdirectory(simple_data_stream)
-add_subdirectory(logging_levels_basic_usage)
-add_subdirectory(logging_levels_custom_sinks)
-add_subdirectory(hello_livekit_sender)
-add_subdirectory(hello_livekit_receiver)
-add_subdirectory(simple_joystick_sender)
-add_subdirectory(simple_joystick_receiver)
-add_subdirectory(ping_pong_ping)
-add_subdirectory(ping_pong_pong)
+add_subdirectory(logging_levels/basic_usage)
+add_subdirectory(logging_levels/custom_sinks)
+add_subdirectory(hello_livekit/sender)
+add_subdirectory(hello_livekit/receiver)
+add_subdirectory(simple_joystick/sender)
+add_subdirectory(simple_joystick/receiver)
+add_subdirectory(ping_pong/ping)
+add_subdirectory(ping_pong/pong)

README.md

@@ -6,6 +6,10 @@ The goal of these examples is to demonstrate common usage patterns of the
 LiveKit C++ SDK (connecting to a room, publishing tracks, RPC, data streams,
 etc.) without requiring users to build the SDK from source.
 
+Related examples are grouped under shared folders. For example, the ping-pong
+examples now live under `ping_pong/`, and paired sender/receiver examples are
+grouped together similarly.
+
 
 ## How the SDK is provided
 
@@ -63,21 +67,27 @@ The Livekit Release SDK is downloaded into **build/_deps/livekit-sdk/**
 
 ### Running the examples
 
-After building, example binaries are located under:
+After building, example binaries are located under their corresponding build
+subdirectories:
 ```bash
-build/<example-name>/
+build/<example-path>/
 ```
 
 For example:
 ```bash
 ./build/basic_room/basic_room --url <ws-url> --token <token>
 ```
 
+Grouped examples follow the same pattern, for example:
+```bash
+./build/ping_pong/ping/PingPongPing --url <ws-url> --token <token>
+```
+
 ### Supported platforms
 
 Prebuilt SDKs are downloaded automatically for:
 * Windows: x64
 * macOS: x64, arm64 (Apple Silicon)
 * Linux: x64
 
-If no matching SDK is available for your platform, CMake configuration will fail with a clear error.
+If no matching SDK is available for your platform, CMake configuration will fail with a clear error.

build.sh

@@ -0,0 +1,51 @@
+#!/usr/bin/env bash
+# Copyright 2026 LiveKit
+#
+# 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.
+
+set -euo pipefail
+
+usage() {
+  cat <<EOF
+Usage: ./build.sh [clean] [--help] [CMAKE_ARGS...]
+
+Options:
+  clean           Remove the build directory before building
+  --help, -h      Show this help message and exit
+
+Extra arguments are forwarded to cmake, e.g.:
+  ./build.sh -DLIVEKIT_SDK_VERSION=0.3.0
+  ./build.sh clean -DCMAKE_BUILD_TYPE=Release
+  ./build.sh -DLIVEKIT_LOCAL_SDK_DIR=<path-to-local-sdk-install-prefix>
+EOF
+}
+
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+BUILD_DIR="${SCRIPT_DIR}/build"
+
+if [[ "${1:-}" == "--help" || "${1:-}" == "-h" ]]; then
+  usage
+  exit 0
+fi
+
+if [[ "${1:-}" == "clean" ]]; then
+  echo "Removing ${BUILD_DIR} ..."
+  rm -rf "${BUILD_DIR}"
+  shift
+fi
+
+mkdir -p "${BUILD_DIR}"
+cd "${BUILD_DIR}"
+
+cmake "${SCRIPT_DIR}" "$@"
+cmake --build . --parallel