[Mesa-dev] Trouble with missing git_sha1.h when building from a fresh tree

[Chad Versace]

On Thu 16 Jun 2016, Emil Velikov wrote:
> On 16 June 2016 at 21:14, Haixia Shi <hshi at chromium.org> wrote:
> > Emil
> >
> > I looked at commit 3689ef32 which started the problem, and it seems that
> > patch removed the line "touch git_sha1.h.tmp". Previously my workflow was
> > "working" because the touch command ensures there's always going to be an
> > empty header file.
> >
> > Was this intentional? For the new git_sha1.h rules, I wonder if it is ok to
> > add a step for git_sha1.h.tmp that does a "touch git_sha1.h" to ensure the
> > file exists?
> >
> As said earlier - if the proposed workflow solutions don't work,
> please check the earlier suggestions/email [1]. Also [2] might be
> mildly related (joking of course)
> 
> Thanks
> Emil
> 
> [1] https://lists.freedesktop.org/archives/mesa-dev/2016-June/120709.html
> [2] https://xkcd.com/1172/

Haixi,

Here is the command to workaround your problems with a git link. After
you copy the source tree MESA_TOP (the original checkout) to TMP_DIR, do
this:

  echo "gitdir: $MESA_TOP/.git" > $TMP_DIR/.git

Then git will treat $TMP_DIR as a fully working git checkout.