blocks|key|3438890|text|Git也有类似的功能，但是您必须通过.gitattributes文件为相关路径专门启用它。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3438891|+++ident
+++++++When+the+attribute+ident+is+set+for+a+path,+git+replaces+$Id$+in
+++++++the+blob+object+with+$Id:,+followed+by+the+40-character+hexadecimal
+++++++blob+object+name,+followed+by+a+dollar+sign+$+upon+checkout.+Any
+++++++byte+sequence+that+begins+with+$Id:+and+ends+with+$+in+the+worktree
+++++++file+is+replaced+with+$Id$+upon+check-in.|code-block|syntax|javascript|3438892|entityMap^0|I|E|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

Git has something similar, but you have to specifically enable it for the relevant paths through the <code>.gitattributes</code> file.

<pre><code> ident
 When the attribute ident is set for a path, git replaces $Id$ in
 the blob object with $Id:, followed by the 40-character hexadecimal
 blob object name, followed by a dollar sign $ upon checkout. Any
 byte sequence that begins with $Id: and ends with $ in the worktree
 file is replaced with $Id$ upon check-in.
</code></pre>

blocks|key|948244|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|948245|旧的，但很有用的answer+about+Git+and+keywords|unordered-list-item|offset|length|948246|Pro+Git，查看“关键字扩展”获得过滤器的帮助(使用过滤器构建|948247|关键字的很好的例子)|948248|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/1792838/enable-ident-string-for-git-repos/1796675#1796675|1|http://progit.org/book/ch7-2.html^0|0|8|T|0|0|0|7|1|0|0^^$0|@$1|2|3|-4|4|5|6|T|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|U|7|@]|8|@$D|V|E|W|1|X]]|9|$]]|$1|F|3|G|4|C|6|Y|7|@]|8|@$D|Z|E|10|1|11]]|9|$]]|$1|H|3|I|4|5|6|12|7|@]|8|@]|9|$]]|$1|J|3|-4|4|5|6|13|7|@]|8|@]|9|$]]]|K|$L|$4|M|N|O|9|$P|Q]]|R|$4|M|N|O|9|$P|S]]]]

<ul>
<li>Old, but useful <a href="https://stackoverflow.com/questions/1792838/enable-ident-string-for-git-repos/1796675#1796675">answer about Git and keywords</a></li>
<li><a href="http://progit.org/book/ch7-2.html" rel="nofollow noreferrer">Pro Git</a>, see "Keywords expansion" for help with filters (with nice example of using filters for $Date$ keyword constructing)</li>
</ul>

blocks|key|951417|text|实际上，当Autoconf运行时，您可以使用M4执行任何命令。因此，你可能想要这样的东西：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|951418|AC_REVISION([m4_esyscmd_s([git+describe+--always])])|code-block|syntax|javascript|951419|请注意，与$Revision$字符串不同，您的configure.ac不会在每次更新树时更改。因此，configure不会在每次更新后重新生成，放入configure的修订版只是为其生成configure的最后一个版本。|offset|length|style|CODE|951420|entityMap^0|0|0|5|A|N|C|1E|9|22|9|2L|9|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]|$I|T|J|U|K|L]|$I|V|J|W|K|L]|$I|X|J|Y|K|L]|$I|Z|J|10|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|N|$]]

You can actually execute any command with M4 when Autoconf runs. Thus maybe you want something like:

<pre><code>AC_REVISION([m4_esyscmd_s([git describe --always])])
</code></pre>

Note that unlike with <code>$Revision$</code> strings your <code>configure.ac</code> will not change every time you update your tree. Hence <code>configure</code> will not get regenerated after each update and the revision put into <code>configure</code> will simply be the last version for which <code>configure</code> was generated.

blocks|key|5052179|text|adl's+answer并不完全是我想要的，但它为我指明了正确的方向。这是我想出来的：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|5052180|将此代码放入configure.ac|style|CODE|5052181|AC_REVISION([m4_esyscmd([./tools/configure.commit])])|code-block|syntax|javascript|5052182|将其另存为tools/configure.commit+(并使其可执行)：|5052183|#!+/bin/sh
#+Display+the+SHA1+of+the+commit+in+which+configure.ac+was+last+modified.
#+If+it's+not+checked+in+yet,+use+the+SHA1+of+HEAD+plus+-dirty.

if+[+!+-d+.git+]+;+then
++#+if+no+.git+directory,+assume+they're+not+using+Git
++printf+'unknown+commit'
elif+git+diff+--quiet+HEAD+--+configure.ac+;+then
++#+configure.ac+is+not+modified
++printf+'commit+%25s'+`git+rev-list+--max-count=1+HEAD+--+configure.ac`
else+#+configure.ac+is+modified
++printf+'commit+%25s-dirty'+`git+rev-parse+HEAD`
fi|5052184|这种组合将把上次修改configure.ac的提交的SHA-1放到configure中，这正是我要找的。但是有一个问题。Git在提交文件时不会触及文件的修改时间。这意味着configure将继续包含AutoConf值，而不是被更新，因为OLDSHA-dirty不会意识到它已经过期。|5052185|你可以用提交后钩子来解决这个问题。将其保存为.git/hooks/post-commit+(并确保将其保存为可执行文件，否则它将无法运行)：|5052186|#!/bin/sh
#
#+Copy+this+to+.git/hooks/post-commit

#+If+configure.ac+was+just+checked+in,+touch+it,
#+so+that+configure+will+be+regenerated+and
#+AC_REVISION+will+reflect+the+new+commit.
#
#+For+some+reason,+--quiet+isn't+actually+quiet,
#+so+redirect+output+to+/dev/null

git+diff-tree+--quiet+HEAD+--+configure.ac+>/dev/null+\
+%7C%7C+touch+-c+configure.ac|5052187|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/8238676/8355^0|0|C|0|0|6|C|0|0|5|M|0|0|A|C|X|9|2D|9|3A|C|0|M|M|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@$A|15|B|16|1|17]]|C|$]]|$1|D|3|E|5|6|7|18|8|@$A|19|B|1A|F|G]]|9|@]|C|$]]|$1|H|3|I|5|J|7|1B|8|@]|9|@]|C|$K|L]]|$1|M|3|N|5|6|7|1C|8|@$A|1D|B|1E|F|G]]|9|@]|C|$]]|$1|O|3|P|5|J|7|1F|8|@]|9|@]|C|$K|L]]|$1|Q|3|R|5|6|7|1G|8|@$A|1H|B|1I|F|G]|$A|1J|B|1K|F|G]|$A|1L|B|1M|F|G]|$A|1N|B|1O|F|G]]|9|@]|C|$]]|$1|S|3|T|5|6|7|1P|8|@$A|1Q|B|1R|F|G]]|9|@]|C|$]]|$1|U|3|V|5|J|7|1S|8|@]|9|@]|C|$K|L]]|$1|W|3|-4|5|6|7|1T|8|@]|9|@]|C|$]]]|X|$Y|$5|Z|10|11|C|$12|13]]]]

<a href="https://stackoverflow.com/a/8238676/8355">adl's answer</a> wasn't quite what I wanted, but it pointed me in the right direction. Here's what I came up with:

Put this in <code>configure.ac</code>:

<pre><code>AC_REVISION([m4_esyscmd([./tools/configure.commit])])
</code></pre>

Save this as <code>tools/configure.commit</code> (and make it executable):

<pre><code>#! /bin/sh
# Display the SHA1 of the commit in which configure.ac was last modified.
# If it's not checked in yet, use the SHA1 of HEAD plus -dirty.

if [ ! -d .git ] ; then
 # if no .git directory, assume they're not using Git
 printf 'unknown commit'
elif git diff --quiet HEAD -- configure.ac ; then
 # configure.ac is not modified
 printf 'commit %s' `git rev-list --max-count=1 HEAD -- configure.ac`
else # configure.ac is modified
 printf 'commit %s-dirty' `git rev-parse HEAD`
fi
</code></pre>

That combination will put the SHA-1 of the commit in which <code>configure.ac</code> was last modified into <code>configure</code>, which is what I was looking for. But there's a problem. Git doesn't touch the modification time of files when it commits them. This means that <code>configure</code> will continue to contain the <code>OLDSHA-dirty</code> value instead of being updated, because autoconf won't realize that it's out of date.

You can solve that with a post-commit hook. Save this as <code>.git/hooks/post-commit</code> (and make sure you <code>chmod</code> it as executable, or it won't run):

<pre><code>#!/bin/sh
#
# Copy this to .git/hooks/post-commit

# If configure.ac was just checked in, touch it,
# so that configure will be regenerated and
# AC_REVISION will reflect the new commit.
#
# For some reason, --quiet isn't actually quiet,
# so redirect output to /dev/null

git diff-tree --quiet HEAD -- configure.ac &gt;/dev/null \
 || touch -c configure.ac
</code></pre>

blocks|key|3439062|text|我试图实现与OP类似的功能；我想将Git+commit-id嵌入到Postgres版本字符串中。Postgres的configure.in中的代码，在我打算修改的同一行中，已经有了一个示例。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3439063|它的要点是，您可以将shell代码片段嵌入到configure.in中的字符串文字中，生成的configure文件(实际上是执行shell脚本的shell+)将始终执行该shell代码片段来构建结果字符串。|offset|length|style|CODE|3439064|请参阅patch。以下是生成的configure文件中configure.in和相关部分的补丁。|3439065|AC_DEFINE_UNQUOTED(PG_VERSION_STR,
-+++++++++++++++++++["PostgreSQL+$PACKAGE_VERSION+on+$host,+compiled+by+$cc_string,+`expr+$ac_cv_sizeof_void_p+\*+8`-bit"],
%2B+++++++++++++++++++["PostgreSQL+$PACKAGE_VERSION+(commit+`cd+$srcdir+&&+git+log+-1+--format=format:%25h`)+on+$host,+compiled+by+$cc_string,+`expr+$ac_cv_sizeof_void_p+\*+8`-bit"],
++++++++++++++++++++[A+string+containing+the+version+number,+platform,+and+C+compiler])|code-block|syntax|javascript|3439066|生成的configure代码：|3439067|+cat+>>confdefs.h+<<_ACEOF
-#define+PG_VERSION_STR+"PostgreSQL+$PACKAGE_VERSION+on+$host,+compiled+by+$cc_string,+`expr+$ac_cv_sizeof_void_p+\*+8`-bit"
%2B#define+PG_VERSION_STR+"PostgreSQL+$PACKAGE_VERSION+(commit+`cd+$srcdir+&&+git+log+-1+--format=format:%25h`)+on+$host,+compiled+by+$cc_string,+`expr+$ac_cv_sizeof_void_p+\*+8`-bit"
+_ACEOF|3439068|补丁前后的Postgres版本字符串：|3439069|PostgreSQL+9.3.0+on+x86_64-unknown-linux-gnu,+compiled+by++...
PostgreSQL+9.3.0+(commit+2cf9dac)+on+x86_64-unknown-linux-gnu,+compiled+by+...|3439070|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/gurjeet/postgres/commit/2cf9dac4bd92d111c1bc6520a4ccfcaf8b9bbef8#diff-1^0|0|M|C|1A|9|0|F|9|R|C|3|5|0|0|0|3|9|0|0|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|15|8|@$D|16|E|17|F|G]|$D|18|E|19|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|1A|8|@$D|1B|E|1C|F|G]|$D|1D|E|1E|F|G]]|9|@$D|1F|E|1G|1|1H]]|A|$]]|$1|J|3|K|5|L|7|1I|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|1J|8|@$D|1K|E|1L|F|G]]|9|@]|A|$]]|$1|Q|3|R|5|L|7|1M|8|@]|9|@]|A|$M|N]]|$1|S|3|T|5|6|7|1N|8|@]|9|@]|A|$]]|$1|U|3|V|5|L|7|1O|8|@]|9|@]|A|$M|N]]|$1|W|3|-4|5|6|7|1P|8|@]|9|@]|A|$]]]|X|$Y|$5|Z|10|11|A|$12|13]]]]

I was trying to achieve something similar as the OP; I wanted to embed Git commit-id in Postgres version string. The code in Postgres' configure.in, in the same line that I intended to modify, already had an example.

The gist of it is that you can embed shell snippet in string literals in <code>configure.in</code>, and the resulting <code>configure</code> file (the shell executing the shell script, actually) will always execute that shell snippet to build the resultant string.

Please see the <a href="https://github.com/gurjeet/postgres/commit/2cf9dac4bd92d111c1bc6520a4ccfcaf8b9bbef8#diff-1" rel="nofollow">patch</a>. Following are the patches to <code>configure.in</code> and relevant section from resulting <code>configure</code> file.

<pre><code>AC_DEFINE_UNQUOTED(PG_VERSION_STR,
- ["PostgreSQL $PACKAGE_VERSION on $host, compiled by $cc_string, `expr $ac_cv_sizeof_void_p \* 8`-bit"],
+ ["PostgreSQL $PACKAGE_VERSION (commit `cd $srcdir &amp;&amp; git log -1 --format=format:%h`) on $host, compiled by $cc_string, `expr $ac_cv_sizeof_void_p \* 8`-bit"],
 [A string containing the version number, platform, and C compiler])
</code></pre>

Resulting <code>configure</code> code:

<pre><code> cat &gt;&gt;confdefs.h &lt;&lt;_ACEOF
-#define PG_VERSION_STR "PostgreSQL $PACKAGE_VERSION on $host, compiled by $cc_string, `expr $ac_cv_sizeof_void_p \* 8`-bit"
+#define PG_VERSION_STR "PostgreSQL $PACKAGE_VERSION (commit `cd $srcdir &amp;&amp; git log -1 --format=format:%h`) on $host, compiled by $cc_string, `expr $ac_cv_sizeof_void_p \* 8`-bit"
 _ACEOF
</code></pre>

Postgres version string before and after the patch:

<pre><code>PostgreSQL 9.3.0 on x86_64-unknown-linux-gnu, compiled by ...
PostgreSQL 9.3.0 (commit 2cf9dac) on x86_64-unknown-linux-gnu, compiled by ...
</code></pre>

blocks|key|5337414|text|为git建立的autoconf解决方案使用的是build-aux/git-version-gen，参见例如。https://github.com/kergoth/autoconf/blob/master/build-aux/git-version-gen|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|5337415|然后，您只需要确保您的标记使用与版本相同的前缀(即v)。|5337416|AC_INIT([GNU+project],++++++++++m4_esyscmd([build-aux/git-version-gen+.tarball-version]),++++++++++[bug-project@example])|5337417|这适用于git和非git版本，其中.version跟踪.git开发版本，而.tarball-version跟踪非git发布版本。|5337418|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/kergoth/autoconf/blob/master/build-aux/git-version-gen^0|N|P|1I|21|0|0|P|1|0|0|3D|0|H|8|11|G|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@$9|W|A|X|1|Y]]|E|$]]|$1|F|3|G|5|6|7|Z|8|@$9|10|A|11|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|12|8|@$9|13|A|14|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|15|8|@$9|16|A|17|B|C]|$9|18|A|19|B|C]]|D|@]|E|$]]|$1|L|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]]|M|$N|$5|O|P|Q|E|$R|S]]]]

The established autoconf solution for git is using <code>build-aux/git-version-gen</code>,
see eg. <a href="https://github.com/kergoth/autoconf/blob/master/build-aux/git-version-gen" rel="nofollow noreferrer">https://github.com/kergoth/autoconf/blob/master/build-aux/git-version-gen</a>

and then you just need you ensure that your tags are using the same prefix (i.e. <code>v</code>) as the version.

<code>AC_INIT([GNU project],
 m4_esyscmd([build-aux/git-version-gen .tarball-version]),
 [bug-project@example])
</code>

This works with git and non-git releases, where <code>.version</code> is tracking the .git dev version, and <code>.tarball-version</code> the non-git release version.

When using <a href="http://www.gnu.org/s/autoconf/" rel="noreferrer">Autoconf</a> in a project managed with <a href="http://subversion.apache.org/" rel="noreferrer">Subversion</a>, I would put this code in <code>configure.ac</code>:

<pre><code>AC_REVISION($Revision: 1234 $)
</code></pre>

With <code>svn:keywords Revision</code>, <a href="http://www.gnu.org/software/autoconf/manual/html_node/Notices.html" rel="noreferrer"><code>AC_REVISION</code></a> would insert the revision number of <code>configure.ac</code> into the generated <code>configure</code> script.

How can I do something similar in a project managed with <a href="http://git-scm.com/" rel="noreferrer">Git</a>?

Git doesn't have keywords like <code>$Revision$</code>, and doesn't have revision numbers as such. But it does have SHA1s for commits, and <code>git describe</code>. I'm just not sure how to incorporate that into <code>configure.ac</code>.

How can I use AC_REVISION with Git?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

在使用托管的项目中使用时，我会将以下代码放在configure.ac中AC_REVISION($Revision: 1234 $)使用svn:keywords Revision，会将configure.ac的修订号插入到生成的configure脚本中。如何在使用管理的项目中执行类似的操作Git没有像$Revision$...

问如何在Git中使用AC_REVISION？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在Git中使用AC_REVISION？EN