From: "Martin Storsjö" <martin@martin.st>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [FFmpeg-cvslog] fftools/graphprint: Now, make it a Killer-Feature!
Date: Fri, 16 May 2025 11:19:27 +0300 (EEST)
Message-ID: <b1a35031-544f-6e47-60a8-679ab945694@martin.st> (raw)
In-Reply-To: <DM8P223MB0365D6A3054B5BE24746A2FFBA93A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>
On Fri, 16 May 2025, softworkz . wrote:
>
>
>> -----Original Message-----
>> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Martin
>> Storsjö
>> Sent: Freitag, 16. Mai 2025 08:22
>> To: ffmpeg-devel@ffmpeg.org
>> Subject: Re: [FFmpeg-devel] [FFmpeg-cvslog] fftools/graphprint: Now, make it a
>> Killer-Feature!
>>
>> On Thu, 15 May 2025, softworkz wrote:
>>
>>> ffmpeg | branch: master | softworkz <softworkz@hotmail.com> | Thu May 15
>> 23:10:02 2025 +0200| [1f2b8d7238eff4ab8a4d8d6177e250b8180d51f4] | committer:
>> softworkz
>>>
>>> fftools/graphprint: Now, make it a Killer-Feature!
>>>
>>> remember this: -sg <= means Show Graph
>>>
>>> Signed-off-by: softworkz <softworkz@hotmail.com>
>>>
>>>>
>> http://git.videolan.org/gitweb.cgi/ffmpeg.git/?a=commit;h=1f2b8d7238eff4ab8a4d
>> 8d6177e250b8180d51f4
>>> ---
>>
>> This broke compilation in a number of configurations:
>>
>> Windows UWP/Phone:
>> https://fate.ffmpeg.org/report.cgi?slot=arm-msvc2022-
>> winphone&time=20250516053009
>>
>> filelauncher.o : error LNK2019: unresolved external symbol ShellExecuteA
>> referenced in function ff_open_html_in_browser
>> ffmpeg_g.exe : fatal error LNK1120: 1 unresolved externals
>>
>> iOS:
>> https://fate.ffmpeg.org/report.cgi?slot=aarch64-apple-darwin-
>> ios18&time=20250516011754
>>
>> src/fftools/graph/filelauncher.c:61:13: error: 'system' is unavailable:
>> not available on iOS
>> 61 | if (system(cmd) != 0)
>> | ^
>> /Users/mstorsjo/Xcode_16.2.app/Contents/Developer/Platforms/iPhoneOS.platform/
>> Developer/SDKs/iPhoneOS.sdk/usr/include/_stdlib.h:184:6:
>> note: 'system' has been explicitly marked unavailable here
>> 184 | int system(const char *) __DARWIN_ALIAS_C(system);
>> | ^
>> 1 error generated.
>>
>> tvOS:
>> https://fate.ffmpeg.org/report.cgi?slot=aarch64-apple-darwin-
>> tvos18&time=20250516014542
>>
>> src/fftools/graph/filelauncher.c:61:13: error: 'system' is unavailable:
>> not available on tvOS
>> 61 | if (system(cmd) != 0)
>> | ^
>> /Users/mstorsjo/Xcode_16.2.app/Contents/Developer/Platforms/AppleTVOS.platform
>> /Developer/SDKs/AppleTVOS.sdk/usr/include/_stdlib.h:184:6:
>> note: 'system' has been explicitly marked unavailable here
>> 184 | int system(const char *) __DARWIN_ALIAS_C(system);
>> | ^
>> 1 error generated.
>>
>> // Martin
>>
>
> Hi Martin,
>
> do you think this is a reasonable condition for Apple in configure?
>
> enable browser_launch
> if test -n "$sysroot"; then
> case "$sysroot" in
> */iPhone*.sdk|\
> */AppleTV*.sdk|\
> */WatchOS*.sdk|\
> */BridgeOS*.sdk)
> disable browser_launch
> ;;
> esac
> fi
This is not how we normally do it. String matching trying to detect things
is generally brittle. If the problem is that we can't compile a call to
system(), the configure check should try to compile a call to system(),
and if that doesn't succeed, avoid compiling the code that does that. That
also works for e.g. ShellExecuteA.
That said, I also agree with everybody else that I'd rather not have
ffmpeg do this at all.
// Martin
_______________________________________________
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:[~2025-05-16 8:19 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250515211148.6C91C4128B8@natalya.videolan.org>
2025-05-15 21:50 ` Ramiro Polla
2025-05-15 21:59 ` softworkz .
2025-05-15 22:13 ` Ramiro Polla
2025-05-15 22:19 ` softworkz .
2025-05-15 22:33 ` softworkz .
2025-05-15 22:34 ` Mark Thompson
2025-05-15 22:43 ` softworkz .
2025-05-15 22:49 ` Ramiro Polla
2025-05-15 23:04 ` softworkz .
2025-05-15 23:29 ` Ramiro Polla
2025-05-16 0:19 ` softworkz .
2025-05-15 22:49 ` softworkz .
2025-05-24 15:54 ` Rémi Denis-Courmont
2025-05-25 10:50 ` softworkz .
2025-05-16 0:00 ` Marton Balint
2025-05-16 0:17 ` softworkz .
2025-05-16 0:27 ` James Almer
2025-05-16 0:32 ` softworkz .
2025-05-16 0:36 ` softworkz .
2025-05-16 0:39 ` James Almer
2025-05-16 0:45 ` Lynne
2025-05-16 0:59 ` softworkz .
2025-05-16 0:54 ` Michael Niedermayer
2025-05-16 1:26 ` softworkz .
2025-05-16 8:43 ` softworkz .
2025-05-16 9:41 ` softworkz .
2025-05-16 9:50 ` Nicolas George
2025-05-16 10:10 ` softworkz .
2025-05-16 11:10 ` Nicolas George
2025-05-16 11:49 ` Michael Niedermayer
2025-05-16 12:03 ` Nicolas George
2025-05-31 21:38 ` softworkz .
2025-05-16 13:42 ` softworkz .
2025-05-16 13:45 ` Nicolas George
2025-05-16 3:39 ` Romain Beauxis
2025-05-16 4:15 ` softworkz .
2025-05-16 5:06 ` softworkz .
2025-05-16 8:11 ` Marton Balint
2025-05-24 16:01 ` Rémi Denis-Courmont
2025-05-25 11:04 ` softworkz .
2025-05-15 21:53 ` James Almer
2025-05-15 21:58 ` softworkz .
2025-05-15 22:00 ` James Almer
2025-05-15 22:02 ` softworkz .
2025-05-16 2:06 ` softworkz .
2025-05-31 21:38 ` softworkz .
2025-05-16 6:22 ` Martin Storsjö
2025-05-16 6:40 ` softworkz .
2025-05-16 7:50 ` softworkz .
2025-05-16 8:13 ` Gyan Doshi
2025-05-16 8:19 ` softworkz .
2025-05-16 8:19 ` Martin Storsjö [this message]
2025-05-16 8:25 ` softworkz .
2025-05-16 8:50 ` Martin Storsjö
2025-05-16 8:55 ` softworkz .
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=b1a35031-544f-6e47-60a8-679ab945694@martin.st \
--to=martin@martin.st \
--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