From: Vagrant Cascadian <vagrant@reproducible-builds.org> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH 1/1] tools/cl2c: Strip full path from input file in embedded Date: Sat, 08 Jan 2022 08:49:00 -0800 Message-ID: <87ee5iuq9v.fsf@ponder> (raw) In-Reply-To: <8735nzbz3r.fsf@ponder> On 2021-11-13, Vagrant Cascadian wrote: > On 2021-10-18, Vagrant Cascadian wrote: >> Without this patch, the full build path gets embedded into various >> binaries shipped in the package, for example, libavfilter.a contains >> a reference to: >> >> #line 1 "/build/1st/ffmpeg-4.3.2/libavfilter/opencl/avgblur.cl" >> >> By not embedding the build path, it makes it easier to recreate the >> build environment and reproduce the build: >> >> https://reproducible-builds.org/docs/build-path/ >> >> Originally submitted to Debian as: >> >> https://bugs.debian.org/985187 >> >> Signed-off-by: Vagrant Cascadian <vagrant@reproducible-builds.org> > > Ping? Happy new year! Anything I can do to help move this patch forward? live well, vagrant >> --- >> tools/cl2c | 4 +++- >> 1 file changed, 3 insertions(+), 1 deletion(-) >> >> diff --git a/tools/cl2c b/tools/cl2c >> index e3f92bab1c..48444e61a7 100755 >> --- a/tools/cl2c >> +++ b/tools/cl2c >> @@ -23,11 +23,13 @@ input="$1" >> output="$2" >> >> name=$(basename "$input" | sed 's/.cl$//') >> +# Avoid embedded the build path, using only the basename of the input file. >> +base_input=$(basename "$input") >> >> cat >$output <<EOF >> // Generated from $input >> const char *ff_opencl_source_$name = >> -"#line 1 \"$input\"\n" >> +"#line 1 \"$base_input\"\n" >> EOF >> >> # Convert \ to \\ and " to \", then add " to the start and end of the line. >> -- >> 2.33.0 _______________________________________________ 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".
parent reply other threads:[~2022-01-08 16:49 UTC|newest] Thread overview: expand[flat|nested] mbox.gz Atom feed [parent not found: <8735nzbz3r.fsf@ponder>]
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=87ee5iuq9v.fsf@ponder \ --to=vagrant@reproducible-builds.org \ --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