Use the version of msys2 included in the runner

[JoeSchiff]

I have been getting this error on the Windows runner:
ERROR: aom >= 2.0.0 not found using pkg-config

I think it is because the paths in PKG_CONFIG_PATH are getting messed up.

ffbuild/config.log says:
Can't find >=.pc in any of /c/cibw/vendor/lib/pkgconfig C \cibw\vendor\lib\pkgconfig;D \a\_temp\msys64\mingw64\lib\pkgconfig;D \a\_temp\msys64\mingw64\share\pkgconfig /usr/lib/pkgconfig /usr/share/pkgconfig

[JoeSchiff]

I got the builds to pass in my fork. I'm just waiting for some more tests to finish. I'll have more info tomorrow

[JoeSchiff]

Notes:

Location of aom.pc:
/c/cibw/vendor/lib/pkgconfig

This message ERROR: aom >= 2.0.0 not found using pkg-config still occurs even when erasing 'PKG_CONFIG_PATH' env var and setting it to:
'PKG_CONFIG_PATH': '/c/cibw/vendor/lib/pkgconfig'

Location of ffbuild/config.log:
/d/a/pyav-ffmpeg/pyav-ffmpeg/build/ffmpeg/build/ffbuild/config.log

msys2 docs:
https://github.com/msys2/setup-msys2?tab=readme-ov-file#release
https://www.msys2.org/docs/filesystem-paths/
https://www.msys2.org/docs/pkgconfig/

Content of aom.pc:

# libaom pkg-config.
prefix=C:/cibw/vendor
exec_prefix=${prefix}
includedir=${prefix}/include
libdir=${exec_prefix}/lib

Name: aom
Description: Alliance for Open Media AV1 codec library v3.2.0.
Version: 3.2.0
Requires:
Conflicts:
Libs: -L${libdir} -laom
Libs.private: -lm -lpthread
Cflags: -I${includedir}

[JoeSchiff]

I'm still testing environ variables.

msys2 release: false. Build passes with:
'PKG_CONFIG_PATH': '/c/cibw/vendor/lib/pkgconfig:C:\\msys64\\mingw64\\lib\\pkgconfig;C:\\msys64\\mingw64\\share\\pkgconfig'

msys2 release: true. Build fails with:
'PKG_CONFIG_PATH': '/c/cibw/vendor/lib/pkgconfig:D:\\a\\_temp\\msys64\\mingw64\\lib\\pkgconfig;D:\\a\\_temp\\msys64\\mingw64\\share\\pkgconfig'

[JoeSchiff]

After removing the aom package from build-ffmpeg.py, the error persists, but with the dav1d package instead. When I removed dav1d, the error persists with the next package. So, I think this has nothing to do with aom. aom is just the first package listed.

[WyattBlue]

If you released this commit on my latest commit, and removed disabled aom on Windows. I'll merge this PR

[JoeSchiff]

Yeah, I removed aom only temporarily to test what would happen. My bad, I should have made that clearer.

This commit includes only what was grabbed from a git clone yesterday and

      - uses: msys2/setup-msys2@v2
          ...
          release: false

[WyattBlue]

Thanks for your help! I'm going to use my commit though because it has a cleaner git history 3c9f47a

[JoeSchiff]

Sounds good. Glad I could help