Skip to content

Support binding generation with system FFmpeg #25

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 24, 2020

Conversation

ldm0
Copy link
Member

@ldm0 ldm0 commented Jun 24, 2020

Fixes #23 .
Adds a new CI job that tests binding generation with FFmpeg install on system.
And currently binding generation procedure is like:
First check if is docs.rs docuement generation, if it is, use special process.
Then check if PKG_CONFIG_PATH is set:

  • If it's set, use the package-config files in that path to generate bindings.
  • If not, first check if system FFmpeg exists.
    • If exists, use the system FFmpeg to generate bindings.
    • If not, git clone the newest FFmpeg from GitHub and build it.

@ldm0 ldm0 force-pushed the systemffmpeg branch 3 times, most recently from ea9d44e to c91bf8b Compare June 24, 2020 16:51
@ldm0 ldm0 self-assigned this Jun 24, 2020
@ldm0 ldm0 added the enhancement New feature or request label Jun 24, 2020
@ldm0 ldm0 force-pushed the systemffmpeg branch 2 times, most recently from dce91b1 to de338fb Compare June 24, 2020 17:06
@ldm0 ldm0 merged commit 5205763 into CCExtractor:master Jun 24, 2020
@ldm0 ldm0 deleted the systemffmpeg branch June 27, 2020 16:42
@ldm0 ldm0 mentioned this pull request Jul 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bring binding generation for libav* installed in system path back
1 participant