All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nanako Shiraishi <nanako3@lavabit.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Eugene Sajine <euguess@gmail.com>,
	Alex Riesen <raa.lkml@gmail.com>,
	git@vger.kernel.org
Subject: Re: ident hash usage question
Date: Wed, 21 Oct 2009 12:09:10 +0900	[thread overview]
Message-ID: <20091021120910.6117@nanako3.lavabit.com> (raw)
In-Reply-To: <7vbpk1lmvl.fsf@alter.siamese.dyndns.org>

Quoting Junio C Hamano <gitster@pobox.com>

> If your product ships as one main executable _dynamically_ linked with two
> dynamic libraries, and all three components are built from the source
> material under your source control, obviously you would need to make sure
> that the above version.o or some equivalent of what embeds output from
> "git describe HEAD" are linked to the main executable and to the two
> libraries, but the idea is the same.

Doesn't the above strategy also apply to the case where the 
libraries are linked statically, too? You get the version 
string from the main program and two version strings from the 
libraries embedded in the final product.

-- 
Nanako Shiraishi
http://ivory.ap.teacup.com/nanako3/

  parent reply	other threads:[~2009-10-21  3:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-20 17:24 ident hash usage question Eugene Sajine
2009-10-20 18:16 ` Alex Riesen
2009-10-20 18:19   ` Alex Riesen
2009-10-20 18:59     ` Eugene Sajine
2009-10-20 19:19       ` Alex Riesen
2009-10-20 20:22         ` Johannes Sixt
2009-10-20 20:35           ` Alex Riesen
2009-10-20 20:30         ` Eugene Sajine
2009-10-20 20:43           ` Junio C Hamano
2009-10-20 22:14             ` Eugene Sajine
2009-10-20 22:30               ` Junio C Hamano
2009-10-20 23:49                 ` Eugene Sajine
2009-10-21  5:35                   ` Daniel Barkalow
2009-10-21  3:09                 ` Nanako Shiraishi [this message]
2009-10-20 20:43           ` Alex Riesen
2009-10-20 22:19             ` Eugene Sajine
2009-10-21  6:25               ` Alex Riesen
2009-10-21 23:32                 ` Eugene Sajine

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20091021120910.6117@nanako3.lavabit.com \
    --to=nanako3@lavabit.com \
    --cc=euguess@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=raa.lkml@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.