Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Александр <cool.ipatovo@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: [FFmpeg-devel] How to enable generation pdb files with msvc toolchain
Date: Fri, 27 May 2022 17:12:03 +0300
Message-ID: <CAAeQ5L7=TKQ01HZYRuhJm8zTyL+U1O-Hooy6CUpGBJuRABxF7Q@mail.gmail.com> (raw)

Hello everybody. I have compiled ffmpeg libraries via msvc toolchain
under win64 os, but I came across on some lack of support pdb files. I need
to use /Zi command with compiler and generate full debug information via
linker's commands /DEBUG:FULL and /PDB:$(NAME), where $(NAME) is the name
of current project (like libavcodec, libavdevice, libavfilter). I have
added these flags via `--extra-cflags` `--extra-ldflags` parameters to
configure.sh script (moreover I patched temporary msvc_common_flags method)
. But unfortunately it has no any results, in my build folder only one
vc140.pdb file was appeared, and each next project's linking overwrites
that file. Maybe is there another "easy" method to generate named pdb files
for each project?
P.S. Sorry for my english, it's a little bit rusty
_______________________________________________
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".

                 reply	other threads:[~2022-05-27 14:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAAeQ5L7=TKQ01HZYRuhJm8zTyL+U1O-Hooy6CUpGBJuRABxF7Q@mail.gmail.com' \
    --to=cool.ipatovo@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