Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Kyle Swanson <k@ylo.ph>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avfilter: add libvmaf_cuda
Date: Thu, 14 Sep 2023 11:59:38 -0700
Message-ID: <CALbjROL3mhLoy1SVsu+MUdNAyDHNs+gGKadvpZweOH-T3ixOsQ@mail.gmail.com> (raw)
In-Reply-To: <a7daf6b8-87bf-a790-fa7c-ea95897f1f04@rothenpieler.org>

[-- Attachment #1: Type: text/plain, Size: 903 bytes --]

Hi,

On Mon, Sep 11, 2023 at 11:51 AM Timo Rothenpieler
<timo@rothenpieler.org> wrote:
>
> On 11.09.2023 19:53, Kyle Swanson wrote:
> > Hi,
> >
> > On Tue, Sep 5, 2023 at 10:16 AM Kyle Swanson <k@ylo.ph> wrote:
> >> I'll merge this in a few days.
> >
> > Not merged yet because I noticed a bug in the configure script.
> > Setting only `--enable-libvmaf` will enable both `libvmaf` and
> > `libvmaf_cuda`. Anyone familiar with the configure script know why
> > this is happening?
>
> require_pkg_config libvmaf [...]
> Should be:
> require_pkg_config libvmaf_cuda [...]
>
> And then you want to also depend on libvmaf_cuda, not libvmaf.

Problem was slightly different, there is no `libvmaf_cuda`, just
`libvmaf` built with the cuda apis optionally enabled. `./configure`
is fixed now and I've tested all the possible combinations, updated
patch attached.

Thanks,
Kyle

[-- Attachment #2: 0001-avfilter-add-libvmaf_cuda.patch --]
[-- Type: application/octet-stream, Size: 11437 bytes --]

[-- Attachment #3: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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:[~2023-09-14 19:00 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-07 17:50 Kyle Swanson
2023-08-14 16:29 ` Kyle Swanson
2023-08-14 17:09 ` Timo Rothenpieler
2023-08-23 20:39   ` Kyle Swanson
2023-08-28 18:54     ` Kyle Swanson
2023-08-28 18:59       ` Timo Rothenpieler
2023-08-28 20:16         ` Kyle Swanson
2023-08-29 17:09           ` Kyle Swanson
2023-08-29 22:14             ` Andreas Rheinhardt
2023-08-30 16:44               ` Kyle Swanson
2023-08-31 18:39                 ` Kyle Swanson
2023-09-05 17:16                   ` Kyle Swanson
2023-09-11 17:53                     ` Kyle Swanson
2023-09-11 18:51                       ` Timo Rothenpieler
2023-09-14 18:59                         ` Kyle Swanson [this message]
2023-09-14 19:10                           ` Timo Rothenpieler
2023-09-15 20:31                             ` Kyle Swanson
2023-09-15 22:33                               ` Timo Rothenpieler
2023-09-18 16:42                                 ` Kyle Swanson
2023-09-18 19:21                                   ` Marvin Scholz
2023-09-18 19:41                                     ` Timo Rothenpieler
2023-09-18 21:39                                       ` Kyle Swanson
2023-09-20 20:06                                         ` Kyle Swanson
2023-09-20 22:54                                           ` Timo Rothenpieler
2023-09-23  9:50                                             ` Kyle Swanson
2023-09-23 11:02                                               ` Timo Rothenpieler
2023-09-25 12:18                                                 ` Kyle Swanson
2023-09-25 16:09                                                   ` Timo Rothenpieler
2023-09-27 17:26                                                     ` Kyle Swanson
2023-08-28 19:05       ` Paul B Mahol

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=CALbjROL3mhLoy1SVsu+MUdNAyDHNs+gGKadvpZweOH-T3ixOsQ@mail.gmail.com \
    --to=k@ylo.ph \
    --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