Migrate Discord backend to concord; switch to Meson + LLVM toolchain #1
Loading…
Reference in a new issue
No description provided.
Delete branch "concord-migration"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Migrate the Discord backend from the in-tree
lib/libdiscordto concord (vendored as a git submodule atlib/concord, pinned to thedevbranch), and switch the build system from CMake to Meson with an LLVM toolchain.Changes
client_discord.cagainst concord's typed API; emoji/guild sync moved intoon_readyvia async REST callbacks; invite URL now resolved from theREADYevent.meson init, plus a custom target that builds concord via its Makefile);native.inipins clang, mold, and LLVM binutils.justfile(lint/format/build),.clang-format,.clang-tidy.src/util.{c,h}; removed duplicated helpers across sources.EVP_Q_digest+ lowercase hex.Verification
ninja -C build→ 0 warnings (clang + mold)clang-tidy -p build src/*.c→ 0 findings insrc/- Replace vendored lib/libdiscord with lib/concord (git submodule, dev branch) - Rewrite the Discord adapter against concord's typed API; move emoji/guild sync into on_ready via async REST callbacks - Switch the build system from CMake to Meson (bootstrapped with meson init) - Add native.ini for the LLVM toolchain (clang, mold, llvm binutils) - Add justfile (lint/format/build) plus .clang-format and .clang-tidy configs - Extract shared helpers into src/util.{c,h}; drop duplicated code - Replace hand-rolled base62 SHA hashing with EVP_Q_digest + lowercase hex - Fix clang-tidy findings (realloc/stream leaks, enum range, tainted index)