build: CLIENT_VERSION etc settings now duplicated in two places #3539

issue laanwj opened this issue on January 14, 2014
  1. laanwj commented at 4:50 PM on January 14, 2014: member

    Since the autotools switch, the values for build-time constants CLIENT_VERSION_* and COPYRIGHT_YEAR are now defined in two places.

    This seems a bit pointless to me. If both places have to be updated for every release, this only gives more values to update (and potentially forget). Or am I misunderstanding something?

    Can we settle on one? If so, which one?

  2. Diapolo commented at 5:16 PM on January 14, 2014: none

    My vote for the clientversion.h.

  3. laanwj commented at 5:36 PM on January 14, 2014: member

    The advantage of putting the version and such at a higher level in the build system is that the version can be used in other generated scripts, and it can be passed as parameter to commands. I guess that was the motivation. It doesn't appear to be used for that right now, though.

  4. theuni commented at 5:39 PM on April 7, 2014: member

    @laanwj I did it this way in the autotools change because I was afraid that some would be nervous about changing too much at once. I had planned a cleanup afterwards that never happened.

    Indeed, it should happen in configure.ac. As you suggested, the reason for doing it here is that it means there's nothing to sync after a bump (installer scripts, packaging, tarball versions, etc.).

    I'll work ok a PR.

  5. fanquake commented at 12:48 PM on May 18, 2017: member

    This was fixed in #10155.

  6. fanquake closed this on May 18, 2017

  7. MarcoFalke locked this on Sep 8, 2021

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-13 15:16 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me