Beeping

beeping-core library

Build with Beeping in C++ Core

The C++20 library every other binding wraps. Clone it, build it from source, and decode a beep with the CLI you compiled — the full cookbook lives on its page.

Your OS:
  1. 01

    Install Git

    setup

    Git is the version-control tool you'll use to download Beeping's source. Cloud SDKs hide this, but the C++ Core is the real engine — you pull it straight from GitHub and build it yourself. This step just makes sure the `git` command exists on your machine; if it's already there it's a no-op.

    git ships with the Xcode Command Line Tools. This pops a system dialog — accept it and let it finish.

    xcode-select --install
  2. 02

    Clone the source

    setup

    This downloads a full copy of the beeping-core repository — the C++20 audio engine that every other Beeping SDK wraps — into a new beeping-core/ folder. Nothing compiles yet; you're just getting the source onto disk so the build tools have something to work with.

    git clone https://github.com/beeping-io/beeping-core.git
  3. 03

    Install CMake & build tools

    setup

    CMake is the build-system generator the project uses: it reads beeping-core's build description and produces the actual compile/link commands for your platform. On macOS the same Homebrew line also installs Conan (the C++ dependency manager), so there's no separate Conan step there; on Linux it also pulls in the GCC compiler via build-essential.

    Homebrew installs CMake and Conan in one go — no separate Conan step on macOS.

    brew install cmake conan
  4. 04

    Compile beeping-core

    setup

    This is the actual build. The first command fetches and compiles every dependency through Conan, then CMake configures the project and compiles the C++ Core from source. A lot of text scrolls past and the first run takes a few minutes — that's normal. When it finishes you'll have a real beeping-core CLI binary that you built yourself.

    Fetch the dependencies and compile. The first build takes a few minutes; a lot of text scrolls past — that's normal.

    cd beeping-core
    ./scripts/conan-install.sh Release
    cmake --preset conan-release
    cmake --build --preset conan-release
    When it finishes you'll have build/Release/cli/beeping-core — that's the decoder you'll run next.
  5. 05

    Decode locally

    playground

    The payoff: you run the CLI you just compiled against a real .wav beep and watch it decode the hidden payload back out — the full round-trip, entirely on your own machine, no cloud. The command below points at a holonet-beep.wav in your Downloads. To get a beep encoded under your own API key (and earn the badge), run the interactive round-trip in the Holonet quest.

    ./build/Release/cli/beeping-core decode ~/Downloads/holonet-beep.wav

Prefer it guided — one step at a time, with a real beep encoded under your own API key and a badge at the end?

🌌 Open the Holonet quest →