All existing jobs use libiio 0.x (distribution package or external/),
so the libiio 1.x code path was never compiled in CI. Add a server-only
Ubuntu job that configures with ENABLE_LIBIIO_V1, lets external/ build
libiio 1.0.0, checks that the 1.x API was selected and builds the
PlutoSDR device library and plugins. It only runs when PlutoSDR or
libiio related files change.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Run the Windows build to completion before invoking the CPack package
target. This avoids a file-access race in which fixup_bundle() attempts
to inspect runtime DLLs in the build/bin directory while DLL-copy
commands may still be running.
The separate steps eliminate the observed libsigmf.dll access failure
with Ninja. The underlying build-ordering issue has not yet been
identified.
Signed-off-by: Robin Getz <rgetz503@gmail.com>
Reject trailing whitespace, including in new files and lines.
Trailing spaces and tabs provide no value, can cause
inconsistent rendering, complicate diffs and merges, and
create needless whitespace-only changes in future edits.
Keeping them out makes source files cleaner and reviews
easier.
Use .gitattributes to limit checks to text files.
Fetch full history to make the PR base and head commits available.
Signed-off-by: Robin Getz <rgetz503@gmail.com>
Normalize existing text files to LF to conform to the repository-wide
line-ending policy defined by .gitattributes by:
git add --renormalize .
Signed-off-by: Robin Getz <rgetz503@gmail.com>
Use an absolute path for the Coverity analysis archive so its
location is independent of the current working directory. This
prevents the archive from being created in the build directory and
then failing subsequent validation and upload steps.
These path issues were not encountered during local testing because
the script's working directory happened to match the expected archive
location. They only surfaced on the GitHub Actions runner, where the
script changes into the build directory before creating the archive.
Also validate directory changes and use the configured Coverity
notification email and properly quoted archive path for uploads.
Signed-off-by: Robin Getz <rgetz503@gmail.com>
Add a daily GitHub Actions workflow that checks (a) the latest SDRangel
revision against the current Coverity analysis and (b) upload quota before
installing dependencies or starting the build. This avoids unnecessary
runner time when the revision has already been analyzed or Coverity is
not accepting submissions.
When analysis is required and permitted, build SDRangel with Coverity,
collect and upload the results for analysis, helping identify newly
introduced defects before they sit in the code base for too long.
Because Coverity Scan submissions are limited, run the analysis only on
master rather than on pull requests.
Signed-off-by: Robin Getz <rgetz503@gmail.com>