Use SetEnvVar instead of appending .bash_profile with LLVM variables

It seems that the existence of .bash_profile on Debian systems prevents
the .profile file from being read on login, which means some additions
to PATH that are essential for e.g. the Web Engine build are not made.

Pick-to: 6.7 6.6 6.5
Change-Id: Ib271ef49e573fc0588ffbaa9bebbfda4469b60f9
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
Reviewed-by: Elias Toivola <elias.toivola@qt.io>
Reviewed-by: Piotr Wierciński <piotr.wiercinski@qt.io>
Reviewed-by: Simo Fält <simo.falt@qt.io>
This commit is contained in:
Michael Brüning
2024-02-19 16:54:31 +01:00
parent e47468b7d9
commit 92969b10f5
2 changed files with 2 additions and 2 deletions

View File

@@ -48,5 +48,5 @@ sudo mv /usr/local/libclang "$destination"
rm -rf $zip
echo "export LLVM_DYNAMIC_LIBS_100=$destination" >> ~/.bash_profile
SetEnvVar "LLVM_DYNAMIC_LIBS_100" "$destination"
echo "libClang for QtForPython= $version" >> ~/versions.txt

View File

@@ -62,5 +62,5 @@ sudo mv /usr/local/libclang "$destination"
rm -rf $zip
echo "export LLVM_INSTALL_DIR=$destination" >> ~/.bash_profile
SetEnvVar "LLVM_INSTALL_DIR" "$destination"
echo "libClang = $version" >> ~/versions.txt