diff options
| author | Jertzukka <Jertzukka@gmail.com> | 2024-07-01 23:35:31 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-07-01 22:35:31 +0200 |
| commit | ca69368ba4ba238a227060d6f4406d6235792a96 (patch) | |
| tree | 05e8bc064876fbdf50846727b4fd7e0143bca14a /src/Crypto/sha256_avx1_x86.asm | |
| parent | 96974169199d347172fc5d4a2924f092d602b3de (diff) | |
| download | VeraCrypt-ca69368ba4ba238a227060d6f4406d6235792a96.tar.gz VeraCrypt-ca69368ba4ba238a227060d6f4406d6235792a96.zip | |
MacOS: Support CommandLineTools for building (#1371)
Full Xcode application which can take up-to 40GB of disk space is not
necessary for building VeraCrypt, rather the CommandLineTools for XCode
are sufficient which only take few gigabytes. Instead of hardcoding the SDK
location, use xcrun --show-sdk-path to support also the CommandLineTools
instance.
The reason for switching the logic for the XCode version is because the
xcodebuild will not report a correct XCode version for the CommandLineTools,
thus it can't be relied for whether to use the -Wl,-ld_classic flags.
Instead, we can just check the ld version in use in the active developer
directory, and see whether we are using dyld (the new) or ld64 (the old).
Diffstat (limited to 'src/Crypto/sha256_avx1_x86.asm')
0 files changed, 0 insertions, 0 deletions