From: James Almer <jamrial@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [FFmpeg-cvslog] avformat/tls_schannel: add DTLS support Date: Sun, 13 Jul 2025 11:12:55 -0300 Message-ID: <90945521-47a2-437f-9359-b689d2a11b68@gmail.com> (raw) In-Reply-To: <1cf96f20-0179-48f5-9a0f-3669c521c959@rothenpieler.org> [-- Attachment #1.1.1: Type: text/plain, Size: 2072 bytes --] On 7/13/2025 8:35 AM, Timo Rothenpieler wrote: > > On 7/13/2025 4:59 AM, James Almer wrote: >> On 7/12/2025 9:32 PM, Michael Niedermayer wrote: >>> On Fri, Jul 11, 2025 at 04:04:17PM +0000, Timo Rothenpieler wrote: >>>> ffmpeg | branch: master | Timo Rothenpieler <timo@rothenpieler.org> >>>> | Tue Jun 24 19:30:19 2025 +0200| >>>> [90fa9636efff84ec5a4b06815722c08188dca551] | committer: Timo >>>> Rothenpieler >>>> >>>> avformat/tls_schannel: add DTLS support >>>> >>>>> http://git.videolan.org/gitweb.cgi/ffmpeg.git/? >>>>> a=commit;h=90fa9636efff84ec5a4b06815722c08188dca551 >>>> --- >>>> >>>> configure | 6 +- >>>> libavformat/tls_schannel.c | 890 +++++++++++++++++++++++++++++++++ >>>> + +++++++---- >>>> libavformat/version.h | 2 +- >>>> 3 files changed, 833 insertions(+), 65 deletions(-) >>> >>> breaks on mingw64 >>> >>> src/libavformat/tls_schannel.c: In function ‘ff_dtls_export_materials’: >>> src/libavformat/tls_schannel.c:606:5: error: unknown type name >>> ‘SecPkgContext_KeyingMaterialInfo’; did you mean >>> ‘SecPkgContext_NegotiationInfo’? >> >> This type (and probably everything below) is API introduced on Windows >> 10, so unless you build targeting _WIN32_WINNT >= 0x0A00, it will not >> be defined. >> So i guess we should make the tls_schannel.c force that value, like so: > > It builds fine for me without doing that. It may be you're using a newer mingw64 release that doesn't wrap those structs and defines in _WIN32_WINNT wrappers whereas Michael is using an older one provided by a stable distro as a crosscompiler package which does. That, or Michael's mingw64 release doesn't even have them, which is the most likely scenario. If it's the latter, then a configure check would need to be added like > check_type "windows.h security.h schnlsp.h" "SecPkgContext_KeyingMaterialInfo" And then make the dtls_protocol depend on it if using schannel, and wrappers added to tls_schannel.c where needed. [-- Attachment #1.2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 495 bytes --] [-- Attachment #2: Type: text/plain, Size: 251 bytes --] _______________________________________________ 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:[~2025-07-13 14:13 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20250711160418.F0282412864@natalya.videolan.org> 2025-07-13 0:32 ` Michael Niedermayer 2025-07-13 2:59 ` James Almer 2025-07-13 6:33 ` Hendrik Leppkes 2025-07-13 11:36 ` Timo Rothenpieler 2025-07-13 11:35 ` Timo Rothenpieler 2025-07-13 14:12 ` James Almer [this message] 2025-07-13 13:55 ` James Almer 2025-07-13 11:34 ` Timo Rothenpieler
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=90945521-47a2-437f-9359-b689d2a11b68@gmail.com \ --to=jamrial@gmail.com \ --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