Build failure about freshplayerplugin

[i-rinat]

Try the latest version from master branch. I think, 934aa9c should fix the build.

[BlackMage2]

I have these too, but if only if I'm building from a different directory than src

[i-rinat]

but if only if I'm building from a different directory than src

That's odd. Although I don't test building from the source directory and always build in a separate directory (usually named build), it shouldn't matter.

As far as I can tell, the issue is related to the FFmpeg headers. There is a transition started years ago, names of various constants got AV_ prefix, i.e. CODEC_CAP_TRUNCATED becoming AV_CODEC_CAP_TRUNCATED and so on. Both sets were there, so applications using FFmpeg were buildable. And now they started to remove old names. I think that will affect other applications too.

I use the latest release of FFmpeg, 3.4.1, and CODEC_CAP_TRUNCATED and the like are still there in the headers. But I think, next release won't have them. Probably, @SolarAquarion is using some development version from their source control repository.

[BlackMage2]

with me, I get exactly these errors only when I build from a different directory than freshplayerplugin/src

when I build in ${i-rinat/freshplayerplugin_REPO_ROOT}/src everything compiles without problems

Summary:
when i build in ${i-rinat/freshplayerplugin_REPO_ROOT}/src it compiles good
when i build ${i-rinat/freshplayerplugin_REPO_ROOT}/ I get the mistakes above

[i-rinat]

when i build in ${i-rinat/freshplayerplugin_REPO_ROOT}/src it compiles good
when i build ${i-rinat/freshplayerplugin_REPO_ROOT}/ I get the mistakes above

That shouldn't matter, unless there are some remainders from previous configurations. CMake projects are not really reconfigurable. So if you some older copy of sources, run cmake there, then update sources and continue to build, there could be build issues. The easiest way is to remove everything CMake generated and start again. That's why README recommends to make directory build and configure/build there. That way all generated files may be removed easily. If one builds directly in source root, generated files are created right there, and may be hard to locate then when one wants to cleanup.

I believe that if you start with a fresh copy of sources, build should succeed in both cases.