Always build vcpkg-tool from souce

[msclock]

I encouter GLIBC-not-found problems such as /usr/lib/libc.so.6: version GLIBC_2.14’ not found` on x86 linux x86_x64 linux. In bootstrap.sh, it always chooses to download vcpkg-tool instead of build from source.

And are there any ways to implement the behaviour?

[bansan85]

Take a look at

vcpkg/scripts/bootstrap.sh

Lines 172 to 188 in 8349779

	vcpkgDownloadTool="ON"
	if [ "$UNAME" = "Darwin" ]; then
	echo "Downloading vcpkg-macos..."
	vcpkgToolReleaseSha=$VCPKG_MACOS_SHA
	vcpkgToolName="vcpkg-macos"
	elif [ "$vcpkgUseMuslC" = "ON" ]; then
	echo "Downloading vcpkg-muslc..."
	vcpkgToolReleaseSha=$VCPKG_MUSLC_SHA
	vcpkgToolName="vcpkg-muslc"
	elif [ "$ARCH" = "x86_64" ]; then
	echo "Downloading vcpkg-glibc..."
	vcpkgToolReleaseSha=$VCPKG_GLIBC_SHA
	vcpkgToolName="vcpkg-glibc"
	else
	echo "Unable to determine a binary release of vcpkg; attempting to build from source."
	vcpkgDownloadTool="OFF"
	vcpkgToolReleaseSha=$VCPKG_TOOL_SOURCE_SHA

You can't decide if you want to build from source or not. But if you are on x86 linux (and not x86_64), you should always build from source.

[msclock]

@bansan85 Sorry for my wrong tying.😓 I reviewed the failed logs https://github.com/msclock/cppcheck-wheel/actions/runs/11927833904/job/33243849191#step:3:399. And it is a x86_64 linux.

it runs on the old image quay.io/pypa/manylinux2010_x86_64:2022-08-05-4535177 of cibuildwheel in ci.

You can't decide if you want to build from source or not.

Yep, the scripts always set it ON for vcpkgDownloadTool. It seems it is a glic download problem that it is not compatible to GLIBC_2.14 from vcpkg baseline.

[msclock]

Finally, I switch to a newer image x86_x64 image. It works.

Anyway, thanks for your explanation.