compiling-diva-projects

Compile Divalto DIVA projects with xwin7.exe and parse compilation reports for errors.

6|Updated May 11, 2026
One-click install
npx skills add https://github.com/divalto/divalto-ia-devkit --skill compiling-diva-projects-divalto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compiling-diva-projects
Source: https://github.com/divalto/divalto-ia-devkit/tree/main/plugins/divalto-devkit/skills/compiling-diva-projects
Command: npx skills add https://github.com/divalto/divalto-ia-devkit --skill compiling-diva-projects-divalto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Compiling Divalto DIVA projects with xwin7.exe involves fragile details: accented profile names fail silently due to encoding, missing users crash the compiler and corrupt compiled objects, and raw compilation logs are hard to interpret. This Skill orchestrates the full compile-and-verify workflow and turns raw reports into structured, actionable error lists. ## Core Features & Use Cases - Standalone harness generation: Generate a mini-project (.dhpt + .dhps) around a single .dhsp/.dhsq source file for a fast ~42s validation loop during iterative development. - Real project compilation: Compile an existing .dhpt via compile_project.py, which writes an ISO-8859-1 PowerShell script so accented profiles like "développement" are recognized, validates the profile against the project before launching, and supports incremental build, full buildall, subproject, and single-source scopes. - Report parsing and diagnosis: Parse xwin7 compilation reports into JSON with summary counts, errors with source-file context, warnings, and specialized diagnosis for "clip grille" screen-mask overflow errors. - Use Case: After editing a .dhsp source file, generate a standalone harness, compile it, and parse the report to get each error with its source file and line context before running a full ERP integration build. ## Quick Start Compile my Divalto project at C:\projets\divalto.dhpt with the développement profile and tell me whether there are any compilation errors.

Frequently Asked Questions about compiling-diva-projects

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I compile a Divalto DIVA project with xwin7?

Run xwin7.exe with -action build or buildall, -project pointing to the .dhpt, -profile with the profile name, and -output for the log file. The compile_project.py script automates this, including correct encoding of accented profile names.

How to quickly validate a single .dhsp file without compiling the whole ERP project?

Use generate_harness.py to create a standalone mini-project (.dhpt + .dhps) around your source file, then run the generated PowerShell compile script. This validation loop takes about 42 seconds versus several minutes for an incremental ERP build.

Why does xwin7 report 'Profil absent du projet' when the profile exists?

The profile name contains an accent (e.g. développement) and the PowerShell script was saved as UTF-8 instead of ISO-8859-1. xwin7 compares profile names as raw ISO-8859-1 bytes, so the é must be encoded as 0xE9, not the two-byte UTF-8 sequence.

Is 'Le projet est à jour, aucune compilation à effectuer' a compilation error?

No, it means an incremental build found nothing to recompile, which is a success state. The parsers report success:true with up_to_date:true; only the summary line Erreur(s)=N with N greater than zero indicates failure.

What happens if I omit the -user parameter when running xwin7?

If -user is omitted and the X_USER environment variable is empty, xwin7 crashes with ExitCode -805306369 and corrupts compiled objects, forcing a full buildall of over 45 minutes. The scripts fall back to the Windows USERNAME to prevent this.

When should I use build versus buildall in xwin7?

Use build for incremental compilation of modified files during development, and buildall for a full recompile after dictionary structure changes or object corruption. A buildall on a subproject is required after .dhsd structure changes so dependent masks are recompiled.