On Tue, Jul 29, 2014 at 2:25 PM, Luca Barbato <[email protected]> wrote:
> On 29/07/14 18:07, Diego Biurrun wrote:
>> This activates the const-enabled zlib API and kills related warnings.
>> ---
>> libavcodec/cscd.c | 11 +++++++----
>> libavcodec/dxa.c | 5 +++--
>> libavcodec/exr.c | 1 +
>> libavcodec/flashsv.c | 1 +
>> libavcodec/flashsvenc.c | 1 +
>> libavcodec/g2meet.c | 1 +
>> libavcodec/lcldec.c | 10 ++++++----
>> libavcodec/lclenc.c | 1 +
>> libavcodec/pngdec.c | 1 +
>> libavcodec/pngenc.c | 1 +
>> libavcodec/svq3.c | 11 ++++++-----
>> libavcodec/tiff.c | 1 +
>> libavcodec/tiffenc.c | 1 +
>> libavcodec/tscc.c | 4 ++--
>> libavcodec/zerocodec.c | 1 +
>> libavcodec/zmbv.c | 4 ++--
>> libavcodec/zmbvenc.c | 4 ++--
>> libavformat/http.c | 1 +
>> libavformat/matroskadec.c | 1 +
>> libavformat/mov.c | 11 ++++++-----
>> libavformat/rtmpproto.c | 11 +++++++----
>> tools/cws2fws.c | 1 +
>> 22 files changed, 54 insertions(+), 30 deletions(-)
>>
>
> Sounds fine, not sure if adding -DZLIB_CONST would work better or worse.
Adding it to the makefiles makes it less likely that some added file
misses to add this define.
Diego, is there any downside to that approach?
--
regards,
Reinhard
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
