Use a workspace

A workspace manifest lists project directories. Each member directory must contain exactly one .bproj manifest.

Prerequisites

Create two project directories. Put one .bproj manifest in each directory. Keep the .bws file at their common root.

Actions

1. Create Workspace.bws:

   workspace {
     name = "Acme"
   }
   
   member "app" {
     path = "app"
   }
   
   member "core" {
     path = "core"
   }

2. Select the application member from a real source path:

   beskid analyze ./app/Src/Main.bd --project ./Workspace.bws --target App --plain

3. Source-path selection chooses the deepest matching member directory. Add --workspace-member app when you must override that result.

4. Use defaultTestMember when selection has no input path and no --workspace-member. Selection otherwise uses the first declared member.

5. Use automatic host target selection only when its App, then Test, then Lib, then remaining-target order fits the task.

6. Pass --target when the manifest has more than one target that could satisfy your task.

Expected result

The source path selects the deepest matching member, which is app in this example. With no input path, selection uses defaultTestMember and then the first declared member. The selected target is the explicit App target.

Recovery

If a directory contains multiple .bws files, keep only the intended workspace manifest or pass its path with --project. If selection is wrong, pass --workspace-member and --target. If a member directory contains zero or multiple .bproj files, fix that member directory before retrying.

Next task

Resolve the selected member’s dependencies and lockfile.