[Sumover-dev] Re: Vic H264 compilation issues

[Andrew Ford]

Hi Piers,

Thanks for the info. The SSL issue I actually only saw in the original Vic
branch, not the 264 branch. There was a -lcrypto right at the end of the
linking step, and apparently there aren't any #includes of SSL header files
since I didn't see any errors in compiling the individual object files. Was
this something that got taken out at one point?

Also, apparently the ffmpeg site is back up now, so I'll try compiling with
that (+ tcl/tk 8.5) on Monday.

--Andrew

2009/3/12 Piers O'Hanlon <p.ohanlon at cs.ucl.ac.uk>

> Hi Andrew,
>
> Thanks for your feedback. The issues you were seeing were largely down to
> changes in ffmpeg - it is a fast changing library. However there was also an
> error in vic' s configure script which I have now corrected - VIC's
> configure script calls ffmpeg's configure script which sets things up so
> that the ffmpeg libraries are installed into the local directory - thus not
> needed root access. I've updated the repository to reflect the updates.
>
> If you want use tcl8.5 then you can configure VIC to use it by calling
> configure in the following way:
> ./configure --with-tk=/usr/share/tcltk/tk8.5/tkConfig.sh
> --with-tcl=/usr/share/tcltk/tcl8.5/tclConfig.sh
>
> I'm not aware of VIC's dependence on openssl - where do you see that?
>
> Thanks,
>
> Piers.
>
> 2009/3/9 Andrew Ford <acf0659 at rit.edu>
>
>  Hi,
>>
>> When I try the --enable-gpl configure option, it seems to fail on trying
>> to checkout ffmpeg like so:
>>
>> checking out HEAD of ffmpeg from  svn://svn.mplayerhq.hu/ffmpeg/trunk...
>> Configuring ffmpeg...
>> ./configure: line 4961: cd: ffmpeg: No such file or directory
>>
>> And then it apparently restarts, gets an error on Tcl/Tk that doesn't
>> happen on the first pass (checking for a compatible version of Tk... test:
>> 4770: ==: unexpected operator) and eventually fails. I tried checking it out
>> myself and setting the path manually (adding --disable-ffmpeg-co), but the
>> directory structure doesn't match what the script is looking for (most
>> recent svn has libavcodec etc in subdirectories) so I ended up just using
>> the ffmpeg version I had from Ubuntu packages.
>>
>> After that, I had to get libpostproc-dev and libswscale-dev to round out
>> ffmpeg, then yasm to compile x264 (side note: had to start doing sudo make
>> at this point since x264's makefile wants to install). Then I had to change
>> line 6 in codec/ffmpeg_codec.h: it was looking for avcodec.h in libavcodec/,
>> whereas the ffmpeg version I have installed just has them in
>> /usr/include/ffmpeg - there's no -I/usr/include/ffmpeg on that g++ call
>> (despite having had configured with --with-ffmpeginc=/usr/include) so I had
>> to change the include to ffmpeg/avcodec.h. Same issue for
>> codec/x264encoder.cpp, codec/rtp_h264_depayloader, render/color-swscale.cpp
>> and similar for video/deinterlace.h where I had to change libpostproc/ to
>> postproc/. Side note: do you think this is just an Ubuntu packaging quirk,
>> or did ffmpeg change its whole directory structure at one time?
>>
>> Lastly I had to move libx264.a from x264/ to x264/lib (linker was
>> expecting the latter, presumably the newer version of x264 changed it), and
>> then it finally finished.
>>
>> Aside from ffmpeg nonsense I've only had a couple other minor compiling
>> issues. Either the original vic branch or the 264 branch needed libssl-dev -
>> a pretty obvious dependency in retrospect, but it's not listed on the AVATS
>> wiki page (http://mediatools.cs.ucl.ac.uk/nets/mmedia/wiki/SvnDev). Also
>> I had an issue with getting the 264 branch to use Tcl/Tk version 8.5 - I'm
>> not sure if that's supported behavior, but it seemed to be ignoring the
>> configure option.
>>
>> --Andrew
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://oakham.cs.ucl.ac.uk/pipermail/sumover-dev/attachments/20090313/2439d8eb/attachment.html