[qtbase] no absolute paths

[autoantwort]

Otherwise the build fails with:

-- Performing post-build validation
warning: There should be no absolute paths, such as the following, in an installed package:
    /Users/leanderSchulten/git_projekte/vcpkg/packages/qtbase_arm64-osx
    /Users/leanderSchulten/git_projekte/vcpkg/vcpkg_installed
    /Users/leanderSchulten/git_projekte/vcpkg/buildtrees/qtbase
    /Users/leanderSchulten/git_projekte/vcpkg/downloads
Absolute paths were found in the following files:
    /Users/leanderSchulten/git_projekte/vcpkg/packages/qtbase_arm64-osx/tools/Qt6/bin/qt-cmake-private
    /Users/leanderSchulten/git_projekte/vcpkg/packages/qtbase_arm64-osx/tools/Qt6/bin/debug/qt-cmake-private
    /Users/leanderSchulten/git_projekte/vcpkg/packages/qtbase_arm64-osx/tools/Qt6/bin/debug/qt-cmake
    /Users/leanderSchulten/git_projekte/vcpkg/packages/qtbase_arm64-osx/tools/Qt6/bin/qt-cmake

And the file content looks like:

#!/bin/sh

# The directory of this script is the expanded absolute path of the "$qt_prefix/bin" directory.
script_dir_path=`dirname $0`
script_dir_path=`(cd "$script_dir_path"; /bin/pwd)`

# Try to use original cmake, otherwise to make it relocatable, use any cmake found in PATH.
original_cmake_path="/Users/leanderSchulten/git_projekte/vcpkg/downloads/tools/cmake-3.25.1-osx/cmake-3.25.1-macos-universal/CMake.app/Contents/bin/cmake"
cmake_path=$original_cmake_path
if ! test -f "$cmake_path"; then
    cmake_path="cmake"
fi

toolchain_path="$script_dir_path/../../../share/Qt6/qt.toolchain.cmake"

# Find the qt toolchain relative to the absolute bin dir path where the script is located.
exec "$cmake_path" -DCMAKE_TOOLCHAIN_FILE="$toolchain_path" -G"Ninja" "$@"

[BillyONeal]

Notably, the failure doesn't happen with the current vcpkg-tool version bootstrap fetches, but it does happen with the soon-to-be-merged copy.

In #31723 I resolved it in favor of turning off the check because the ultimate goal, relocatablity, is maintained without any edits, as the absolute path is just an attempted search location.

However, I think this resolution is reasonable too; I don't have strong opinions on it.

See also, kf5i18n with a very similar 'absolute path then fallback' behavior for Python.

[autoantwort]

The problem is that if we disable the check it will also not report the cases that are preventing relocatablity in the future.

[BillyONeal]

The problem is that if we disable the check it will also not report the cases that are preventing relocatablity in the future.

Yeah, I understand, that's why I'm not opposed to this. Just wanted to make sure this was considered.

[Adela0814]

CI failed, please find the details from https://dev.azure.com/vcpkg/public/_build/results?buildId=90161&view=artifacts&pathAsName=false&type=publishedArtifacts.
CI failures:

CMake Error at ports/qtbase/portfile.cmake:475 (file):
  file failed to open for reading (No such file or directory):

    D:/packages/qtbase_x64-windows/tools/Qt6/bin/qt-cmake
Call Stack (most recent call first):
  ports/qtbase/portfile.cmake:481 (remove_original_cmake_path)
  scripts/ports.cmake:147 (include)

[autoantwort]

@Adela0814 I have fixed the ci errors

[BillyONeal]

Thanks!