Bug 726 - can't opt-out of re-configure when git head changes
Summary: can't opt-out of re-configure when git head changes
Status: RESOLVED DUPLICATE of bug 1283
Alias: None
Product: libsigrok
Classification: Unclassified
Component: Build system (show other bugs)
Version: unreleased development snapshot
Hardware: All All
: Normal normal
Target Milestone: ---
Assignee: Daniel Elstner
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-31 09:20 CET by Wolfram Sang
Modified: 2020-04-05 15:42 CEST (History)
1 user (show)



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Wolfram Sang 2015-12-31 09:20:32 CET
Since commit 7f289d14e ("Build: Append git revision hash to version") a
complete reconfigure is necessary whenever git HEAD changes. This makes sense
for users just wanting to use top of tree. But it is extremly annoying for
developers; e.g. I just had a series of 5 smaller commits to one driver which I
wanted to buildtest before sending out.

I'd like to be able to opt-out of this behaviour by some configure-switch.

For those looking for a quick fix, simply delete the line starting with
CONFIG_STATUS_DEPENDENCIES in your Makefile.
Comment 1 Daniel Elstner 2015-12-31 16:28:10 CET
I agree it's annoying, but I dislike the idea of developers opting out of this since it kind of defeats the purpose of the whole thing. Actually the re-configure is not the main problem. Rather, the problem is that the git-derived version number is put into a header file all source files depend on.

This requires two fixes: One in Autoconf to avoid placing the version into config.h, for which I actually have a patch pending. And another in libsigrok, changing the internal includes in such a way that the version number is not pulled in from everywhere.

If you just want a quick hack-around, I guess something like

    make -j4 CONFIG_STATUS_DEPENDENCIES= all

may work, without having to change any files (untested).
Comment 2 Wolfram Sang 2016-01-01 16:47:10 CET
Thanks for the heads up on this matter.

Your workaround is better, of course. I can even put it into my configs for per-project make setups :)
Comment 3 Uwe Hermann 2020-04-05 15:42:34 CEST
Merging this with #1283, which has a patch series pending as fix, which will get merged soon.

*** This bug has been marked as a duplicate of bug 1283 ***