From: "L. E. Segovia" <amy@amyspark.me>
To: ffmpeg-devel@ffmpeg.org
Subject: [FFmpeg-devel] [PATCH v4 0/1] configure: Set WIN32_LEAN_AND_MEAN at configure time
Date: Mon, 14 Aug 2023 08:53:22 -0300
Message-ID: <143a582d-f746-4bed-b670-13e1374bd6c9@amyspark.me> (raw)
In-Reply-To: <13ea8238-3765-4d29-a176-d6543e3dc4b9@amyspark.me>
Now adapted to insert WIN32_LEAN_AND_MEAN for MinGW and Cygwin too.
L. E. Segovia (1):
configure: Set WIN32_LEAN_AND_MEAN at configure time
compat/atomics/win32/stdatomic.h | 1 -
compat/w32pthreads.h | 1 -
configure | 3 +++
libavdevice/dshow_capture.h | 1 -
libavdevice/opengl_enc.c | 1 -
libavfilter/vsrc_ddagrab.c | 1 -
libavformat/os_support.c | 6 ++----
libavutil/wchar_filename.h | 1 -
libswscale/utils.c | 1 -
9 files changed, 5 insertions(+), 11 deletions(-)
--
2.41.0
_______________________________________________
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:[~2023-08-14 11:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 18:51 [FFmpeg-devel] [PATCH] os_support, network: Fix build failure on Windows with BZIP2 L. E. Segovia
2023-07-29 18:48 ` [FFmpeg-devel] [PATCH v2] " L. E. Segovia
2023-08-04 12:36 ` [FFmpeg-devel] [PATCH] " Martin Storsjö
2023-08-04 12:39 ` Martin Storsjö
2023-08-05 13:00 ` L. E. Segovia
2023-08-05 20:47 ` [FFmpeg-devel] [PATCH v3 0/1] configure: Set WIN32_LEAN_AND_MEAN at configure time L. E. Segovia
2023-08-14 11:53 ` L. E. Segovia [this message]
[not found] ` <cover.1692013786.git.amy@amyspark.me>
2023-08-14 11:53 ` [FFmpeg-devel] [PATCH v4 1/1] " L. E. Segovia
2023-08-14 19:58 ` Martin Storsjö
2023-08-19 15:31 ` Gyan Doshi
2023-08-19 21:12 ` Martin Storsjö
[not found] ` <cover.1691268056.git.amy@amyspark.me>
2023-08-05 20:47 ` [FFmpeg-devel] [PATCH v3 " L. E. Segovia
2023-08-14 11:30 ` Martin Storsjö
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=143a582d-f746-4bed-b670-13e1374bd6c9@amyspark.me \
--to=amy@amyspark.me \
--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