Add Cloud Agent development environment config - #2
Open
kumagi wants to merge 1 commit into
Open
Conversation
Co-authored-by: Hiroki KUMAZAKI <rintyo_@hotmail.com>
kumagi
marked this pull request as ready for review
August 19, 2026 14:34
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a Cloud Agent development environment configuration (
.cursor/environment.json) fortinylamb, a C++20 RDBMS built with CMake.The environment uses Cursor's default image plus an idempotent
installstep that installs the toolchain and tools the project needs:build-essential+libstdc++-14-dev— C++20 toolchain and thelibstdc++dev files clang selects (the default image shipslibgcc-14-devbut notlibstdc++-14-dev, which otherwise breaks linking withcannot find -lstdc++).cmake,ninja-build,clang— the build system and compiler used by CI and the README.clang-format— required by theclang-formatCI check.postgresql-client—psqlfor exercising the PostgreSQL-wiretinylamb_server.curl,git,ca-certificates— for the pinned GoogleSQL / googletest / TPC-H DBGEN downloads CMake performs.The build downloads its dependencies (pinned GoogleSQL
execute_querybinary with SHA-256 verification, googletest v1.14.0 viaFetchContent, and the TPC-H DBGEN source) over the network, so no vendored deps are required.Validation
FetchContentbuild compiledparser/tokenizer.cppand ranparser/tokenizer_test.cppunderctest— all 6 cases passed.installis idempotent (second run reports0 added, 0 removed).Note on repository build state
The full project does not build at the current
master(d37c659):CMakeLists.txtandREADME.mdreference roughly 60 source files that are not committed to the repository — the entireserver/andbenchmark/directories plusquery/sql_engine.cpp,query/googlesql_*.cpp, severalexecutor/,expression/, andplan/sources. CMake configuration therefore fails before any target can be built. This is a codebase issue independent of the environment; once those sources are committed, the configured environment builds and tests the project with the standardcmake -S . -B build -G Ninja && cmake --build build -j && ctest --test-dir buildflow.