2 Commits

Include renames

Author	SHA1	Message	Date
octoturgeandClaude Sonnet 5.5	fdc99582e1	Check out the sibling repos the proxy's path dependencies need ... The first CI run built OpenSSL fine and then failed: Cargo.toml depends on ../continuum-schemas and ../continuum-common, which the runner's checkout of the proxy alone did not have. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>	2026-10-29 11:02:23 +00:00
octoturgeandClaude Sonnet 5.5	2bbe8af9a1	Build discover_printers for Windows on the Gitea runner ... SSDP can only be tried on a machine that shares the printers' network segment, and the development container is a router hop away. This builds the existing discover_printers example as a Windows .exe and uploads it as a CI artifact, with a README for whoever runs it and a SHA-256 file. Uses the windows-latest self-hosted runner continuum-cad already uses (Windows PowerShell 5.1, MSVC present, upload-artifact@v3 only). The proxy links OpenSSL directly and Windows has none, so the job builds it with vcpkg (x64-windows-static-md, linked into the .exe) in a directory of its own, away from the CAD pipeline's. The job smoke-runs the exe, then runs the discovery tests on Windows after the upload, so a Windows-only test failure turns the job red without withholding the executable. Not run anywhere yet: this container cannot build for Windows (no MSVC or mingw). The first CI run is the first real build. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>	2026-10-29 10:54:07 +00:00