ClosedBit Guide Part 3: Building From Studio

#Part 3. Building From Studio

The Studio Console is the normal build surface. Open it, type help, then run the command that matches the output you want.

Command	Result
`check`	Checks the current source
`save`	Saves the editor file
`compile cba input.cbp output.cba`	Builds a runtime package
`compile exe input.cbp output.exe`	Builds a Windows app
`compile dll input.cbp output.dll`	Builds a Windows DLL
`compile library input.cbp output.cbl`	Builds a ClosedBit library
`compile linux input.cbp output-folder`	Builds the Linux beta package folder
`encrypt input output key`	Encrypts a package
`decrypt input output key`	Decrypts a package

Example:

compile exe app.cbp bin/app.exe small graphics threaded msi

Flags describe the package shape and runtime profile. small and chunky conflict. fps and ai conflict. msi only belongs with compile exe.

Flag	Use it when
`small`	Download size matters
`chunky`	You want fewer launch buffers and fewer page-fault spikes
`compute`	The app is math, data, or tooling heavy
`graphics`	The app opens windows or draws frames
`fps`	Frame pacing matters more than AI cache behavior
`ai`	Tagged retrieval, parsing, or generation is the hot path
`threaded`	Runtime worker scheduling helps the workload
`usage_high`	Local speed matters more than quiet CPU behavior
`max_memory 1024`	You need a guarded memory budget in MB
`uncapped`	You are running a trusted local stress test
`msi`	You want the `.exe` wrapped as a Windows installer