Skip to content
GPPL IDESOLIDCAM / INVENTORCAM

Search installation, settings, features and diagnostic codes.

Tab to a result · Enter to open · Esc to close
Install Community ↗

PRO projects

The workflow requires a PRO beta package supplied to you and an active license. Keep project files on a local Windows drive.

  1. Use File → Open Folder to open the directory containing your postprocessor.
  2. Open the main .gpp file.
  3. Check that the status bar says GPPL IDE: Pro.
  4. Open the GPPL Project view in Explorer and expand the main file to inspect its includes.

PRO can index a workspace folder without a manifest. A gppl.project.json makes the project name, root, entry points, exclusions, and disk-reading encoding explicit.

Run SolidCAM GPPL: Create gppl.project.json. The command uses the first workspace folder, opens an existing manifest if present, or creates a template. Review the generated entry point: the command chooses an open .gpp under that folder, which may not be your intended main file.

A minimal explicit configuration is:

{
"schemaVersion": 1,
"name": "My machine postprocessor",
"root": ".",
"entryPoints": ["MyMachine.gpp"],
"encoding": "windows1252",
"exclude": ["archive/**"]
}

Save this as gppl.project.json beside MyMachine.gpp. Use valid JSON without comments or trailing commas.

Field Meaning
schemaVersion Supported schema version: 1.
name Project label in Explorer.
root Project directory, resolved relative to the manifest. Use . for the same directory.
entryPoints Main .gpp paths relative to root; helps resolve ambiguous main-file candidates.
encoding Encoding used to read unopened project files.
exclude Additional scanning exclusions within the project.

Keep the root within your intended local workspace. Setting a manifest root is not a way to enable network access.

The generated template also contains variants, traces, documentation, and delivery. In this feature set, those fields are accepted but do not enable processing, trace execution, documentation generation, or packaging. You can omit them from a minimal manifest.

Workspace discovery checks each workspace folder and its immediate child directories for manifests. If projects are nested more deeply, open the actual project folder in VS Code.

The Explorer updates after indexing and file changes. Use SolidCAM GPPL: Refresh Project Explorer to refresh the displayed tree. If a structural configuration change is not reflected, run Developer: Reload Window to rebuild the workspace state.

An unsupported schema version or invalid JSON causes the manifest to be ignored. Check server logs when the project behaves like an ordinary workspace folder.

Continue with Includes and cross-file navigation.