Closed mrturcot closed 1 year ago
There's a build option to set it to "UNKNOWN", but the fallback is to run version.py which actually does respect SOURCE_DATE_EPOCH. (version.sh does not, but that is only used by waf).
There's a build option to set it to "UNKNOWN", but the fallback is to run version.py which actually does respect SOURCE_DATE_EPOCH. (version.sh does not, but that is only used by waf).
thanks alright well I tried exporting with zshrc
export SOURCE_DATE_EPOCH="${SOURCE_DATE_EPOCH:-$(date +%s)}"
export BUILD_DATE="$(date --utc --date="@${SOURCE_DATE_EPOCH:-$(date +%s)}" +%Y-%m-%d)"
➜ env|grep EPOCH
SOURCE_DATE_EPOCH=1667214429
➜ env|grep BUILD
BUILD_DATE=2022-10-31
reloaded env, re-emerged mpv but it still shows UNKNOWN.... any chance you could throw me a bone and let me know how I can do this? Thanks :)
Hello is there anyway we could add a build-date USE flag with meson "option('build-date', type: 'boolean', value: true, description: 'whether to include binary compile time')" because as now mpv -v shows "[cplayer] built on UNKNOWN"
compiling manually with that option I get "[cplayer] built on Sun Oct 30 12:34:35 2022"
Just nicer to keep track. Thanks for considering!