Databases
StackOverflow2013
Postsdbo
POWriting Version Info into Comment Block
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWriting Version Info into Comment Block
    primarykey
    data
    text
    <blockquote> <p><strong>Possible Duplicate:</strong><br> <a href="https://stackoverflow.com/questions/2253953/how-do-i-embed-mercurial-tags-into-my-c-c-code">How do I embed Mercurial tags into my C/C++ code?</a> </p> </blockquote> <p>Can I add version control info from Mercurial into the 1st comment block in the .c and .h files that the repo is tracking?</p> <p>I assume it will involve adding something to the Makefile, such that a comment line in the source files gets substituted on each compilation with the latest version information</p> <p>I have got as far as passing in a #define from the compiler (e.g. gcc -D) and have added the following to my Makefile:</p> <pre><code>HGVERSION:= $(shell hg parents --template 'hgid: {node|short}') CFLAGS += -g -Wall -DHGVERSION="\"${HGVERSION}\"" </code></pre> <p>but although this makes the preprocessor variable available to me, I'm not sure this helps with inserting some text into a comment block.</p> <p>To elaborate, I can see how I can use HGVERSION to implement say a -ver flag to get the exe to printout its version info, but I can't see how to get that info into the actual text of the source files</p> <p>To elaborate, I can see how I could use HGVERSION to implement some sort of programatic version information, e.g. printing the version when running the exe with a -ver flag or something like that, but not how I can get that info into the actual source file text in some way</p> <p>I'd like to end up with something like this at the top of each of my src files:</p> <pre><code>/* some comments * * version x.y.z */ </code></pre> <p>Am I on the right track or is some other technique required here?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USbph
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTDuplicate
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COI'm not sure it is an exact duplicate (I did find that same link to Mercurial wiki in my in my research). I'm trying to write it into a comment block in the source file, not use it programatically, i.e. not as a #define value used in a C statement.
      singulars
      1. POWriting Version Info into Comment Block
      1. USbph
    2. COCheck the [Keyword](http://mercurial.selenic.com/wiki/KeywordExtension) extension. But also read [Why You Don't Need It](http://mercurial.selenic.com/wiki/KeywordPlan#head-2007fad6f31bf6f1f1b5c3d5b02e5c6225de3ec5).
      singulars
      1. POWriting Version Info into Comment Block
      1. USSome programmer dude
    3. CO@JoachimPileborg I thought the same until yesterday when I realised we may have a use case where a customer gets some header files outside of any cloned repo (they just get a bunch of files) as they're not intersted in recompiling or doing any development. In this instance it would be useful (as a belt and braces approach) to be able to link the file they have to an update in our repo. Granted we should keep a record of exactly what we deliver and when, but as I say its a belt and braces thing
      singulars
      1. POWriting Version Info into Comment Block
      1. USbph
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload