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

Emil Velikov emil.l.velikov at gmail.com
Thu Jun 16 19:47:31 UTC 2016


On 16 June 2016 at 20:42, Haixia Shi <hshi at chromium.org> wrote:
> Bisect shows the problem started at commit
> 3689ef32afdafbb030069e560aac0e563fc29048
> Author: Emil Velikov <emil.velikov at collabora.com>
> Date:   Mon May 30 12:32:05 2016 +0100
>
>     automake: rework the git_sha1.h rule, include in tarball
>
>     As we'll need the file in the release tarball, rework the rule so that
>     the file is regenerated _only_ if we're in a git repository.
>
>     With this in place we can build vulkan (anv) from a release tarball.
>
>     Cc: Jason Ekstrand <jason.ekstrand at intel.com>
>     Cc: Kristian Høgsberg Kristensen <krh at bitplanet.net>
>     Signed-off-by: Emil Velikov <emil.velikov at collabora.com>
>
> I'm not building from a release tarball, but the workflow first copies the
> source tree to a tmp directory (without the .git directory), so there's no
> git_sha1.h file, and the file is not generated either.
>
Hmmm... I wouldn't have imagine this particular workflow. Have you
considered gitlink and/or git worktree ?

If neither of these are an option for you see my earlier email.

-Emil


More information about the mesa-dev mailing list