Skip to content

build-all.sh fails in Step 1 because bbdev/api/pyproject.toml does not exist #28

@DYCSchool

Description

@DYCSchool

./scripts/nix/build-all.sh fails because it expects bbdev/api/pyproject.toml, but that file does not exist in the current bbdev submodule.

 =========================================================================
 ==== BUCKYBALL SETUP STEP 1: bbdev install
 =========================================================================

Installing bbdev Python dependencies...
Using CPython 3.13.11 interpreter at: /work/buckyball/result/bin/python3
Creating virtual environment with seed packages at: .venv
warning: Failed to hardlink files; falling back to full copy. This may lead to degraded performance.
         If the cache and target directories are on different filesystems, hardlinking may not be supported.
         If this is intentional, set `export UV_LINK_MODE=copy` or use `--link-mode=copy` to suppress this warning.
 + pip==26.0.1
Activate with: source .venv/bin/activate
error: File not found: `pyproject.toml`

In bbdev/api, I can see files like package.json, pnpm-lock.yaml, and requirements.txt, but not pyproject.toml.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions