adding libvpx support about ffmpeg-feedstock HOT 10 CLOSED

You got a little bit further than I did. Also having trouble building the recipe locally, though I see it runs fine on Circle-CI.

from ffmpeg-feedstock.

You can run the same script we run in circle ci on your Linux too. You need to have docker installed though.

from ffmpeg-feedstock.

Sounds like there is something off with your compiler. errno.h is provided by the system. In any event, as @183amir has said you can try with our docker container. In fact, you can run ./ci_support/run_docker_build.sh from the top level directory of the feedstock (assuming you have docker properly installed and running).

from ffmpeg-feedstock.

Ok, are there instructions somewhere on setting up docker and ci for conda-forge? I've never used either. (I'm on OSX by the way.)
Also, I'm a bit confused with the compiler thing since I was using the conda-forge gcc. I actually just discovered if I switch back to my system compiler and configure/build again I get much further, make dies with:

Undefined symbols for architecture x86_64:
  "_x264_encoder_open_138", referenced from:
      _X264_init in libx264.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [libavcodec/libavcodec.56.dylib] Error 1

from ffmpeg-feedstock.

I think we are using Mac's ancient gcc, which is kind of bad. We should probably switch to clang. Travis CI is using XCode 6.1 if you want to try and imitate it. No need to use Docker if you are trying to get a Mac build.

from ffmpeg-feedstock.

Is it using Mac's ancient gcc or a gcc from Anaconda defaults? @jjhelmus indicated that the conda-forge "policy" (provisionally!) was to try to get all OSX builds using gcc. This has advantages and disadvantages. I'm not coming down on either side, but it would be good to have clarification -- even if the policy for now is that we aren't setting a firm policy on this question yet. cc @pelson

from ffmpeg-feedstock.

This recipe is making use of gcc from Anaconda defaults. Generally we have been compiling things with clang (https://github.com/conda-forge/toolchain-feedstock/blob/master/recipe/activate.sh#L3). I don't know the detail on this feedstock as to why the gcc package was used.

from ffmpeg-feedstock.

Not sure I remember either at this point, but it should be fixed to use clang.

from ffmpeg-feedstock.

Though I don't see any C++ linkages FWIW. IIUC FFMPEG is basically C and some Assembly.

from ffmpeg-feedstock.

PR ( #27 ) uses clang. Once that is merged we will be back to using Mac's system compiler, which should hopefully make this easier to tackle.

from ffmpeg-feedstock.