[FFmpeg-devel] Builds for MAC
Hi Would you be interested in me making additional unofficial mac builds for you to add to the downloads page? I have an intel mac, and I should be getting a sillicon mac soon so I can make builds for ARM (unlike the existing person) The only provider listed stated that he would not be offering silicon mac downloads, but I could get something to work. While the intel binaries do work for now, you can expect Apple to cut that off soon like they did when they switched from PPC to Intel. He also seems to be complaining about the traffic load, so another download site would distribute the cost more equally and take some of the costs off him so he can keep his service running. I can also do windows builds as well, but there are already some builders. ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH] configure: Fix some unsafe shell practices
On 2021-07-01 14:20, Leo Izen wrote:
This commit fixes some unsafe shell pratcies in ./configure,
particularly those that involve variable expansions on possibly
unsanitized data in unsafe ways. This commit corrects this behavior
in a small number of locations.
---
configure | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/configure b/configure
index b124411609..dd910f538f 100755
--- a/configure
+++ b/configure
@@ -530,7 +530,7 @@ warn(){
die(){
log "$@"
-echo "$error_color$bold_color$@$reset_color"
+echo "$error_color$bold_color$*$reset_color"
cat < If you think configure made a mistake, make sure you are using the
latest
@@ -625,7 +625,7 @@ set_weak(){
}
sanitize_var_name(){
-echo $@ | sed 's/[^A-Za-z0-9_]/_/g'
+printf %s "$*" | sed 's/[^A-Za-z0-9_]/_/g'
}
set_sanitized(){
@@ -1091,7 +1091,7 @@ check_cmd(){
cmd=$1
disabled $cmd && return
disable $cmd
-test_cmd $@ && enable $cmd
+test_cmd "$@" && enable $cmd
}
check_as(){
@@ -1100,7 +1100,7 @@ check_as(){
code=$2
shift 2
disable $name
-test_as $@ < $TMPH
+echo "static const $struct_name * const ${name}[] = {" > $TMPH
for c in $*; do
if enabled $c; then
case $name in
LGTM
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH 1/3] avformat/flv: add support for h265 streams
On 2021-07-01 12:58, Derek Buitenhuis wrote: On 7/1/2021 5:25 PM, Thomas Volkert wrote: I was also about to prepare a discussion mail against this patch set. We shouldn't fuzzy the spec. So.. +1 for skipping this patch set. Hard NAK from me as well. We've rejected essentially this same thing several times, and the reasonign has not changed. Yeah i'm going to have to agree with Derek on this one, and you know when me and Derek agree on the same thing, it's probably the right thing. We should not be extending FLV in incompatible ways (which adding an ID would be). Frankly, people should not be using HEVC, VPx, or Opus in RTMP (I assum this is the intent of this) Agree. either. - Derek ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe". ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
