Skip to content

VPAAMP-392 osx build failure (l1test)#1506

Merged
pstroffolino merged 1 commit into
dev_sprint_25_2from
feature/VPAAMP-392-follow-up
May 22, 2026
Merged

VPAAMP-392 osx build failure (l1test)#1506
pstroffolino merged 1 commit into
dev_sprint_25_2from
feature/VPAAMP-392-follow-up

Conversation

@pstroffolino
Copy link
Copy Markdown
Contributor

Reason for Change: apply identical framework-vs-homebrew detection logic to utests/run.sh so it behaves consistently with install_aampcli.sh

Reason for Change: apply identical framework-vs-homebrew detection logic to run.sh so it behaves consistently with install_aampcli.sh

Signed-off-by: Philip Stroffolino <philip_stroffolino@cable.comcast.com>
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR fixes an OS X L1 test build failure by making test/utests/run.sh detect GStreamer the same way as scripts/install_aampcli.sh: prefer the official macOS GStreamer framework if present, otherwise fall back to Homebrew (and fail early with a clear install message if neither is available).

Changes:

  • Add GStreamer framework-vs-Homebrew detection on macOS for PKG_CONFIG_PATH setup in test/utests/run.sh.
  • Include gst-plugins-base pkg-config path when using Homebrew to ensure gstreamer-app-1.0 can be resolved.
  • Improve failure behavior by emitting an explicit “GStreamer not found” error instead of letting CMake fail opaquely.

@pstroffolino pstroffolino merged commit a3e53e1 into dev_sprint_25_2 May 22, 2026
14 checks passed
@pstroffolino pstroffolino deleted the feature/VPAAMP-392-follow-up branch May 22, 2026 20:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants