From: Timo Rothenpieler <timo@rothenpieler.org> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] Request: make framepool visible externally Date: Tue, 12 Jul 2022 19:15:41 +0200 Message-ID: <0f329e74-fd66-3dd1-043f-0e077f267402@rothenpieler.org> (raw) In-Reply-To: <1645351900.763634.1657643310996@mail.yahoo.com> On 12.07.2022 18:28, Marco Vianini wrote: > Hi all > I'm using Libav libraries (version 4.1.6) to make operations on audio/video AVFrame: conversions, decoding, encoding, etc. That is a really old version, and you should desperately update. > To improve performances I'd like to use framepool. > So I need to include "libavfilter/framepool.h", but I cannot, because this file is not exported. > Should be possible to add "framepool.h" to HEADERS in "libavfilter\Makefile" ? > Code:"NAME = avfilterDESC = FFmpeg audio/video filtering library > HEADERS = avfilter.h \ buffersink.h \ buffersrc.h \ version.h \ framepool.h framepool.h is not a public header, and contains no publicly exported functions. Even if you got the header, you couldn't use the functions since they're not exported from the library. So no, you can't use any of the stuff in there outside of libavfilter. It's also not in any way stable, so can break its API at any random point. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2022-07-12 17:15 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <1645351900.763634.1657643310996.ref@mail.yahoo.com> 2022-07-12 16:28 ` Marco Vianini 2022-07-12 17:15 ` Timo Rothenpieler [this message] 2022-07-13 8:21 ` Marco Vianini 2022-07-12 17:19 ` James Almer 2022-07-13 8:03 ` Marco Vianini 2022-07-13 12:01 ` James Almer 2022-07-13 15:59 ` Marco Vianini
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=0f329e74-fd66-3dd1-043f-0e077f267402@rothenpieler.org \ --to=timo@rothenpieler.org \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git