Installation

Requirements

Different tasks need different tools. Only the first is required to build tcli itself; the rest are needed by the project artifacts tcli scaffolds and runs.

Building tcli

• Go 1.25+ to build the binary.

Building scaffolded C/C++ artifacts (libraries, tools, extensions)

• CMake 4.1+ — the generated CMakePresets.json pins this minimum.
• Ninja — the generated presets use the Ninja generator.
• A supported C++ compiler: MSVC (cl.exe) on Windows or GCC on Linux. No other compiler is supported.
• On Windows, run builds from a Visual Studio / Build Tools developer environment so cl.exe and the INCLUDE/LIB paths are on your environment.
• A valid Teamcenter installation reachable via TC_ROOT: scaffolded libraries and ITK tools compile and link against Teamcenter headers and libraries (ITK executables also need lib/itk_main.obj).

Building or deploying Active Workspace kits/modules

• An Active Workspace install under %TC_ROOT%\aws2\stage, plus its build toolchain.

Deploying and exporting configuration

• A Windows cmd.exe environment and a Teamcenter install: the shipped deploy scripts are .cmd files that call %TC_DATA%\tc_profilevars.bat.
• TC_ROOT, TC_DATA, and UPG available to the run. See Environment resolution.

Initializing a project

• git — tcli init initializes a Git repository.

Build from source

go build -o bin/tcli.exe ./cmd/tcli

Or use the Makefile target:

make build

This produces the tcli binary (bin/tcli.exe on Windows). Put it on your PATH, or invoke it by its full path.

Verify

tcli --help

Running tcli with no arguments launches the terminal UI.