How to "prettify" FFmpeg binary like the pre-compiled Windows build

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

How to "prettify" FFmpeg binary like the pre-compiled Windows build

Hashim Aziz
Hi,

I managed to successfully compile a version of FFmpeg with a MinGW-w64 toolchain on Cygwin, but the resulting binary doesn't look as good as I'd like it to, especially compared with the pre-compiled builds for Windows offered by Zeranoe. Here's an image comparing the two (first run is the pre-compiled Zeranoe build, second is my own binary):

[cid:5d96e204-eb73-4e81-816a-768c3b14fab0]

How did the compilers of this build manage to:

  1.  Remove all configuration options from the banner except the --enable-library options?

  1.  Append the date that the binary was compiled on after the GCC version?

I'm assuming these are options passed to GCC or the preprocessor that I'm unaware of, but maybe it's more involved than that.

Please note: I'm aware of the --no-banner switch but completely removing the banner is not what I'm after here.

Thanks in advance.

_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".

HCFZn.jpg (711K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: How to "prettify" FFmpeg binary like the pre-compiled Windows build

Carl Eugen Hoyos-2
2019-04-05 0:52 GMT+02:00, Hashim Aziz <[hidden email]>:

> Hi,
>
> I managed to successfully compile a version of FFmpeg with a MinGW-w64
> toolchain on Cygwin, but the resulting binary doesn't look as good as I'd
> like it to, especially compared with the pre-compiled builds for Windows
> offered by Zeranoe. Here's an image comparing the two (first run is the
> pre-compiled Zeranoe build, second is my own binary):
>
> [cid:5d96e204-eb73-4e81-816a-768c3b14fab0]
>
> How did the compilers of this build manage to:
>
>   1.  Remove all configuration options from the banner
> except the --enable-library options?

He is using native instead of cross-compilation, therefore he
doesn't use the cross-compilation specific options that are
(nearly) the only difference, he also has only static
libraries in his linking path and therefore has not reason
to pass additional options to the linker.

>   1.  Append the date that the binary was compiled on
> after the GCC version?

This date is printed by his gcc binary when doing "gcc -v" (or similar),
we removed the building date from the binary some time ago to
make the builds reproducible (iirc).

Carl Eugen
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".