Skip to content

docs: clarify public source build path#482

Draft
Bortlesboat wants to merge 2 commits into
altic-dev:mainfrom
Bortlesboat:docs/clarify-public-build-path
Draft

docs: clarify public source build path#482
Bortlesboat wants to merge 2 commits into
altic-dev:mainfrom
Bortlesboat:docs/clarify-public-build-path

Conversation

@Bortlesboat

Copy link
Copy Markdown

Summary

  • add a short note that public source builds should use Xcode or the documented xcodebuild command
  • clarify that the top-level ./build.sh script is for the private Fluid Intelligence build setup, not the OSS build path

Closes #471

Verification

  • git diff --check
  • reviewed the README diff

@grohith327 grohith327 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Bortlesboat Can you update the shell script to skip Fluid Intelligence and attempt to build, you can add the instruction back into the README

@Bortlesboat

Bortlesboat commented Jul 1, 2026

Copy link
Copy Markdown
Author

Updated in aa66718. The top-level ./build.sh now defaults to the public OSS build, skips the private Fluid Intelligence path, and invokes the unsigned macOS xcodebuild command. ./build.sh fi still preserves the private FI build route. I also added the ./build.sh instruction back to the README.

Verified with bash -n build.sh and a fake xcodebuild shim to confirm the public path reaches the build command. I can't run a real Xcode build from this Windows/WSL environment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants