From: Matthew White via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: Matthew White <mehw.is.me@inventati.org>
Subject: Re: [FFmpeg-devel] [PATCH] configure: autodetect libglslang ldflags
Date: Mon, 22 Jan 2024 19:49:45 +0100
Message-ID: <20240122194938.4c560f1b@pineapple> (raw)
In-Reply-To: <NomI70c--3-9@lynne.ee>
> This is very very cursed. Fitting for the public API of the world's fifth worst library.
> Debian is stuck on version 13, so the majority of users are still stuck on version 13.
> Debian ships a pkg-config file, but of course it's incorrect, if you try to compile against it.
> Oh, and libshaderc in Debian ships with a bug such that it segfaults on init, so it's
> not like you can avoid that. And that package's pkg-config file got broken in the past.
>
> I think this is fine for now. I'll let it be discussed for a few more days before merging it.
Thanks for explaining.
By the way, the patch of mine is just a quick fix to not break the FFmpeg's configuration
process when enabling glslang, `./configure --enable-libglslang`, while either libglslang
up to release 13.1.1 or since 14.0.0 is installed in the system.
Accepting only glslang version 14.0.0 and above (--enable-libglslang) will obsolete this
patch: stub flags/libraries "-lOSDependent -lHLSL -lOGLCompiler" may just be dropped.
If useful, this patch is trivial even to backport, I am currently applying it to v6.1.1.
_______________________________________________
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:[~2024-01-22 18:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 6:51 Matthew White via ffmpeg-devel
2024-01-22 12:17 ` Timo Rothenpieler
2024-01-22 12:20 ` Martin Storsjö
2024-01-22 14:34 ` Matthew White via ffmpeg-devel
2024-01-22 14:10 ` Matthew White via ffmpeg-devel
2024-01-22 17:58 ` Lynne
2024-01-22 18:49 ` Matthew White via ffmpeg-devel [this message]
2024-01-22 21:19 ` Martin Storsjö
2024-01-31 16:00 ` Lynne
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=20240122194938.4c560f1b@pineapple \
--to=ffmpeg-devel@ffmpeg.org \
--cc=mehw.is.me@inventati.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