Dear Ali,
> Is the Turing Codec interface patch going to be pushed after the fix of flag
> problem ?
The problem with the static flag is already fixed in the current version of the
patch (v12). If you want to test it, you can manually copy the patch and apply
it on top of the latest ffmpeg HEA
2017-07-17 14:19 GMT+03:00 Saverio Blasi :
> >> Thanks a lot, this makes sense. I thought that flag was compulsory and
> therefore we only included linking against libraries in "Libs.private" in
> the pc file. I have just pushed a fix to the Turing repo to include that in
> the Libs as well.
> >>
>> Thanks a lot, this makes sense. I thought that flag was compulsory and
>> therefore we only included linking against libraries in "Libs.private" in
>> the pc file. I have just pushed a fix to the Turing repo to include that in
>> the Libs as well.
>>
>> I have tested this and it seems to wor
>>In other words, it's just an example in the wiki. It's one way to do it, but
>>that doesn't mean it's *the* way to do it. Building against dynamic libs is
>>certainly much more common if those are (at least for the most part) provided
>>by the "system" (distribution or what have you).
>>
>>Bot
On Wed, Jul 05, 2017 at 17:42:31 +0100, Derek Buitenhuis wrote:
> Passing --static to pkg-config is the de-facto way to build FFmpeg
> with static libraries.
In other words, it's just an example in the wiki. It's one way to do
it, but that doesn't mean it's *the* way to do it. Building against
dyn
On 7/5/2017 5:36 PM, wm4 wrote:
> These pkg-config flag additions in the Ubuntu instructions are pretty
> unusual.
Passing --static to pkg-config is the de-facto way to build FFmpeg
with static libraries.
- Derek
___
ffmpeg-devel mailing list
ffmpeg-dev
On Wed, 5 Jul 2017 15:49:53 +
Saverio Blasi wrote:
> >>2. Not used --pkg-config-flags--static and thus missed including the
> >>(unfortunately non-namespaced) embedded boost libraries.
> >>
> >>I followed the example instructions in
> >>https://trac.ffmpeg.org/wiki/CompilationGuide/Ubuntu#f
>>2. Not used --pkg-config-flags--static and thus missed including the
>>(unfortunately non-namespaced) embedded boost libraries.
>>
>>I followed the example instructions in
>>https://trac.ffmpeg.org/wiki/CompilationGuide/Ubuntu#ffmpeg (at the top of
>>the page it says "Compile FFmpeg on Ubuntu,
2. Not used --pkg-config-flags--static and thus missed including the
(unfortunately non-namespaced) embedded boost libraries.
I followed the example instructions in
https://trac.ffmpeg.org/wiki/CompilationGuide/Ubuntu#ffmpeg (at the top of the
page it says "Compile FFmpeg on Ubuntu, Debian, or
On 7/5/2017 3:56 PM, Saverio Blasi wrote:
> RUN cmake -DCMAKE_INSTALL_PREFIX="/source/ffmpeg/ffmpeg_build" .. && \
> make && \
> make install
> WORKDIR /source/ffmpeg
> COPY 0001-Added-Turing-codec-interface-for-ffmpeg.patch /source/ffmpeg
> RUN git apply 0001-Added-Turing-codec-interface-f
>>So I did try to build this, but the ffmpeg configure check apparently fails
>>at picking it up and dumps 3.5MB of C++ linker errors into the config.log.
>>And I have no idea why it does that. configure actually prints "ERROR:
>>libturing not found using pkg-config", but the .pc part seems to b
On Tue, 4 Jul 2017 14:54:31 +
Saverio Blasi wrote:
> - This patch contains the changes to interface the Turing codec
> (http://turingcodec.org/) with ffmpeg. The patch was modified to address the
> comments in the review as follows:
> - Added a pkg-config file to list all dependencies re
- This patch contains the changes to interface the Turing codec
(http://turingcodec.org/) with ffmpeg. The patch was modified to address the
comments in the review as follows:
- Added a pkg-config file to list all dependencies required by libturing.
This should address the issue pointed out by
13 matches
Mail list logo
