From 9dff6acc556c9e7e2eb5ae4ddc5f3310d8e9eb94 Mon Sep 17 00:00:00 2001 From: Andrew Kaster Date: Thu, 19 Aug 2021 22:33:06 -0600 Subject: Ports: Use new CMakeToolchain.txt located in the build directory Now that we're generating the CMake toolchain file in the build directory, we need to redirect the ports that use CMake to the new location. Looking into this showed that there's still a bunch of work to do in general to make the ports agnostic to which toolchain they're using, there's a lot of hard-coded ${ARCH}-pc-serenity-gcc assumptions still here. --- Ports/libuv/package.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'Ports/libuv') diff --git a/Ports/libuv/package.sh b/Ports/libuv/package.sh index e2114e1fa1..617c9abde8 100755 --- a/Ports/libuv/package.sh +++ b/Ports/libuv/package.sh @@ -4,7 +4,7 @@ version=b12699b1efabfd241324f4ab6cfd6ce576db491e useconfigure=true files="https://github.com/libuv/libuv/archive/$version.tar.gz $port-$version.tar.gz bbbfa2bb50437047efc8fb29c243c914ae0de94107d7cc641c2f84e292904eb5" auth_type=sha256 -configopts="-DCMAKE_TOOLCHAIN_FILE=$SERENITY_SOURCE_DIR/Toolchain/CMake/CMakeToolchain.txt -GNinja" +configopts="-DCMAKE_TOOLCHAIN_FILE=${SERENITY_BUILD_DIR}/CMakeToolchain.txt -GNinja" configure() { run cmake $configopts . -- cgit v1.2.3