PyCForge SDK

Create conversion extensions using the installed PyCForge engine. This short guide is available before an engine is connected.

Find PyCForge

The startup panel searches your saved connection and common Python installations. Choose among several engines, or use Locate PyCForge if it cannot be found. Select the installation, Python environment, installed Crucible support folder or Python interpreter. The custom picker has drive shortcuts. A source folder alone needs a working installed engine.

Continue offline opens local projects and any cached reference. Engine and tools exposes advanced interpreter and compiler settings. This Python selects the SDK interpreter; Refresh checks it. PyCForge’s About → Distribution → SDK Python shows its exact interpreter.

Learn from your engine

After connection, the Help topic selector offers the SDK guide and conversion-import manuals supplied by PyCForge’s Crucible folder. Authoring forms, operation choices and starter projects also come from that installation. Refresh after updating PyCForge. Cached guides remain readable offline; their engine and connection state are displayed above.

Open Engine reference → Conversion coverage to see the advertised families, profiles, exact operation signatures, limitations and starter choices. Search the tree or select a profile. The Authoring methods tab explains the public calls. Python and command-line clients use the same SDK.coverage() and coverage report. Older engines may supply forms and starters without a family overview; that missing metadata is labeled. Browsing cached coverage never approves verification or packaging.

Author and check

Choose New or Open, edit the declaration and Help, save, then Scan. Verify fixtures explicitly converts, compiles and runs the saved examples. Ready to package means the current saved project matches passing evidence for its declared fixtures and recorded environment. Package and registration are separate actions. Changes to projects or tools require fresh verification.

Recovery

Activity contains diagnostics. Unsaved edits and outside file changes clear readiness. A failed refresh preserves compatible cached reference; it cannot authorize execution. Closing during work requests cancellation and waits for the worker. Windows direct-process termination does not supervise arbitrary descendant process trees.

Keyboard

Ctrl+N: New; Ctrl+O: Open; Ctrl+S: Save; F5: Scan; F6: Verify fixtures; Ctrl+B: Package; F1: Help.

With PCFC11, verification also records its external GCC executable. A changed or missing backend requires fresh verification. Use a compatible engine and driver, or select GCC directly on an older engine.