beskid new

Informative guide. This Book page explains Beskid but does not define the standard. For normative requirements, use the Beskid Standard.

Hand-rolling App.bproj is educational exactly once. After that, use beskid new.

What new covers

The new subcommand lists, installs, and instantiates templates for:

• Projects (with sensible project / target / dependency stubs)
• Workspaces (when you already know you live in monorepo hell)
• Individual items (files/modules) inside an existing tree

See new command and project scaffolding.

Typical first project

From an empty directory (flags exact names in reference):

beskid new console --name MyApp --output ./MyApp

console is a template short name. The required --output flag selects the destination. The generated manifest filename follows its project name, so this example should produce MyApp.bproj, a source tree, and entry paths that resolve. If it does not, your template checkout is stale, not your moral failure.

Corelib on new projects

New projects expect the standard library to be reachable: tooling may materialize corelib via bundled templates (corelib command). When developing corelib itself, point BESKID_CORELIB_SOURCE at your checkout.

When not to use templates

• You are merging into an existing repo with established layout conventions.
• You are converting a foreign build system, read resolution before forcing paths.

Next

Fetch, lock, update