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 15:34:09 +0100
Message-ID: <20240122153409.318a74cd@pineapple> (raw)
In-Reply-To: <69fee92-3969-d1a3-59e6-5a7d5baada1@martin.st>
> Also, how does this work when cross compiling - won't the "glslang" binary
> be for the foreign cross target? Or is it something like the sdl-config
> script which is a local shell script that can give relevant build flags (a
> design preceding pkg-config)?
I don't have an answer to that, in FFmpeg's configure I saw using something like
`[ -x "$(command -v gzip)" ] && enable gzip`, so I replicated it to check on the
glslang's binary. I guess that who is ready to cross compile may try this patch
with glslang installed to tell what's happening.
I worked on this fix in GNU/Linux Gentoo. Trying both glslang 14.0.0 and 13.1.1
only the latter requires "-lOSDependent -lHLSL -lOGLCompiler". I configured the
compilation with `./configure --enable-libglslang`, the stub flags/libraries are
not required for glslang 14.0.0. I can compile FFmpeg 6.1.1 by backporting this
patch.
This patch may be dropped altogether by locking FFmpeg on glslang 14.0.0 and up,
and removing the stub "-lOSDependent -lHLSL -lOGLCompiler" flags/libraries.
_______________________________________________
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 14:34 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 [this message]
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
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=20240122153409.318a74cd@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