Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Practice2001 via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: Practice2001 <cordacct2001@gmail.com>
Subject: [FFmpeg-devel] [PATCH] configure: fix static library suffix for MSVC builds
Date: Sun, 23 Nov 2025 05:21:14 +0530
Message-ID: <20251122235114.7725-1-cordacct2001@gmail.com> (raw)

MSVC static builds currently always use ".a" for static library suffixes
(e.g. libavcodec.a, libavformat.a). This causes failures when linking
with Visual Studio, which expects ".lib" static libraries.

This patch adjusts configure so that when --toolchain=msvc is used,
LIBSUF is correctly set to ".lib" instead of the Unix default ".a".

This fixes linking with MSVC and Visual Studio-based build systems.

---

Environment:
 - Windows 10
 - MSYS2 (mingw64)
 - Visual Studio 2019 / 2022
 - NASM installed
 - MSVC toolchain selected

Commands:

    ./configure --toolchain=msvc --enable-static --disable-shared
    make

Resulting static libraries incorrectly have ".a" suffix, e.g.:

    libavcodec.a
    libavformat.a
    libavutil.a

Linking test program with MSVC:

    cl test_ffmpeg.c /I C:\ffmpeg-test-install\include ^
        /link /LIBPATH:C:\ffmpeg-test-install\lib avcodec.lib avformat.lib avutil.lib

Error:

    LINK : fatal error LNK1181: cannot open input file 'avcodec.lib'

---

Verification of the fix:

After applying this patch and rebuilding:

Generated static libraries:

    avcodec.lib
    avformat.lib
    avutil.lib

Test program build script (build_test.bat):

    cl test_ffmpeg.c ^
        /I C:\ffmpeg-test-install\include ^
        /link /LIBPATH:C:\ffmpeg-test-install\lib ^
        avcodec.lib avformat.lib avutil.lib

Output:
	D:\ffmpeg\temp>.\buid_test.bat
	Microsoft (R) C/C++ Optimizing Compiler Version 19.50.35718 for x64
	Copyright (C) Microsoft Corporation.  All rights reserved.

	test_ffmpeg.c
	Microsoft (R) Incremental Linker Version 14.50.35718.0
	Copyright (C) Microsoft Corporation.  All rights reserved.

	/out:test_ffmpeg.exe
	/LIBPATH:C:\ffmpeg-test-install\lib
	avcodec.lib
	avformat.lib
	avutil.lib
	/OUT:test.exe
	test_ffmpeg.obj

	=== BUILD SUCCESS ===
	Running test...
	FFmpeg avcodec version: 4068196
	FFmpeg avformat version: 4064871
	FFmpeg avutil version: 3936868

This confirms MSVC accepts the .lib suffix and the libraries function
correctly.

Closes: #11242
---
 configure | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/configure b/configure
index 47f9b31439..596d66ce53 100755
--- a/configure
+++ b/configure
@@ -6067,7 +6067,7 @@ case $target_os in
     win32|win64)
         disable symver
         LIBPREF=""
-		LIBSUF=".lib"
+        LIBSUF=".lib"
         if enabled shared; then
             # Cannot build both shared and static libs with MSVC or icl.
             disable static
-- 
2.34.1

_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

             reply	other threads:[~2025-11-22 23:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-22 23:51 Practice2001 via ffmpeg-devel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-11-22 23:50 Practice2001 via ffmpeg-devel

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=20251122235114.7725-1-cordacct2001@gmail.com \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=cordacct2001@gmail.com \
    /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