Add build/pkg-install.sh.

[dot-asm]

Compile latest release tag and install it as pkg-config package.

[dot-asm]

To give it a shot execute following commands

mkdir -p /tmp/foo/include
mkdir -p /tmp/foo/lib/pkgconfig
curl -sSf https://raw.githubusercontent.com/dot-asm/blst/pkg-install.sh/build/pkg-install.sh | env PKG_CONFIG_PATH=/tmp/foo/lib/pkgconfig sh`

Examine /tmp/foo tree structure and cleanup as deemed appropriate.

[arrowd]

Bumped into this when porting libblst to FreeBSD. For now I just added my own .pc file to the downstream package, so it'd be great to have this PR merged in.

[erikd]

The git tag version is currently v0.3.16 and the leading v messes up version comparisons.

I had to modify that line to:

  tag=`git tag --sort=v:refname | tail -1 | sed "s/^v//"`

[dot-asm]

This breaks the next line. I've pushed a fixup...

[erikd]

So glad to have found this. Saved me at least half an hour.

[arrowd]

Can we please have a way to override invoking git via env vars?

[dot-asm]

I genuinely don't understand. What is the goal? Why specifically via environment variables? Note that git is used to figure out version...

[arrowd]

I want to package blst in a downstream project (FreeBSD). Package building infrastructure usually disable any networking access during the build, so in this case I'd need a way to prevent this script from calling git.

[dot-asm]

If $SRC is assigned, it's a local directory, so that git won't use network.

[arrowd]

It is still has to be a git repository. At least RPM and FreeBSD ports do not usually use git to fetch the distribution files, so in these contexts there would be no git repo at all.

[dot-asm]

FreeBSD ports do not usually use git to fetch the distribution files,

But they have to use something and hence they could use git. Yes, it would be unusual, but in the essence it's just a download.

Again, the suggested script uses git for unambiguous versioning while also preserving custody. It's argued that it's reasonable trade-off for the unconventional download method.

[arrowd]

There are common and established ways to build software (meson, CMake, git tags and GitHub releases, etc.), which are easily connected to downstream package building infrastructures. When a project goes its own way with custom building scripts it immediately makes it much harder to be properly packaged. But that's my problem anyways, so do whatever you want.