Hive Hive
Sign in
Overview
Projects
Domains
Forage
Flights
Specs
Postmortems
Drops

Add possibility for custom .build folder location

GitHub issue · Closed

Metadata
Source
tuist/tuist #6009
Updated
Jun 25, 2026
Domains
Cache
Details

What problem or need do you have?

Have a feature to customise the location of Tuist/.build folder via command line parameter

macOS version

14.3.1

Tuist version

4.3.4

Xcode version

15.3

Flights

Investigate, reproduce, or fix this item in an isolated repository. Each Flight preserves its outcome and agent session.

New Flights are paused Configure model inference, GitHub, and a sandbox provider to start another Flight. Existing results remain available below.
No Flights yet

Start a Flight and preserve its objective, outcome, and session here.

Comments
P
pepicrft Mar 1, 2024

@mihaicris-adoreme do you mind adding some context around why the following is needed:

Have a feature to customise the location of Tuist/.build folder

It’ll be useful for anyone picking this issue to better understand where the suggestion comes from.

MA
mihaicris-adoreme Mar 10, 2024

Sure. I am working with git worktrees (more clones of the same repo, in order to work on several branches in paralel). I have in each worktree a Tuist/.build folder, but I would like to have tuist working with a shared folder, not depending of the worktree path. Somehow similarly with DerivedData, which might be shared or relative to the project.

D
dosubot[bot] Sep 11, 2025

Hi, @mihaicris-adoreme. I’m Dosu, and I’m helping the tuist team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You requested a feature to customize the location of the Tuist/.build folder via a command line parameter.
  • The goal is to support shared build folders across multiple git worktrees, avoiding separate .build folders per worktree.
  • You provided context explaining the use case involves working on parallel branches with git worktrees.
  • The feature would be similar to how DerivedData can be configured in Xcode.
  • The issue remains unresolved with no further updates or progress.

What’s Next:

  • Please let me know if this feature is still relevant to your workflow with the latest version of Tuist by commenting on this issue.
  • If I don’t hear back within 7 days, I will automatically close this issue to keep the backlog manageable.

Thanks for your understanding and contribution!