macOS desktop: rules/export build a Windows kicad-cli path (backslashes, %TEMP%)
adom-aiflow-jlcpcb rules (and, by the strings in the binary, export) assume a Windows desktop: on a macOS target the DRC call fails with
ERROR: rules check: no DRC report came back: sh: \Applications\KiCad\KiCad.app\Contents\MacOS\kicad-cli: command not found
The kicad-cli path is joined with backslashes, and the temp folder comes from echo %TEMP%. Target: macOS 26.2 arm64, KiCad 10.0.8 at /Applications/KiCad, Adom Bridge 2.1.203 (kicad_readiness reports kicadCli /Applications/KiCad/KiCad.app/Contents/MacOS/kicad-cli). adom-aiflow's own adom-aiflow-kicad-cli-remote handles macOS correctly (~/.adom-aiflow-kicad job folder), so reusing it would fix both verbs.
Workaround used on the board: JLCPCB BOM (Comment, Designator, Footprint, LCSC Part #) and CPL (Designator, Mid X, Mid Y, Layer, Rotation) written by a script that matches every non-EasyEDA footprint's pads to the part's EasyEDA footprint (LCSC library) to get the rotation and origin offset.
1 Reply
Log in to reply.