How to distinguish development version based on each commit build?

[stefanos82]

I compile audacious from source and one thing that is a bit annoying is that we do not distinguish which version is which, based on commit build.

This is what we see in About:

and this is what can be seen in Settings window:

Is it possible to include the commit from git log -1 --oneline | awk '{print $1}' in build process?

[mschwendt]

You could do that and pass it to configure --with-buildstamp=XXX ...

[stefanos82]

Would not make much more sense to have this configuration setup by default when building from source and turn it off when building a release version? It would help with bug reporting.

[stefanos82]

Another thing I have noticed is that there is no development information about anything you may look for, either in https://audacious-media-player.org/developers or in https://audacious-media-player.org/download, and you are left alone in the dark.

[radioactiveman]

What information are you missing there? Feel free to prepare some docs or readme as first step. Any support here is highly appreciated.

[stefanos82]

Even though I have experience with programming, it was not clear, at least to me, how to build audacious and audacious-plugins with custom options, without reading the actual meson.build and meson_options.txt files.

If README got some love with updates, it would help.

As far as I can tell, the INSTALL file has instructions for configure, not for meson, which is sad because it's very user-friendly comparing it with configure...

[stefanos82]

OK, in case anyone wants to use the commit hash in their build via meson, they have to run

# version 1
meson setup builddir -D buildstamp=$(git log -1 --oneline | awk '{print $1}')

# version 2 (preferred)
meson setup builddir -D buildstamp=$(git rev-parse --short HEAD)

at least in a GNU / Linux environment.