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).
Github PR: https://github.com/veracrypt/VeraCrypt/pull/953
* Create CompilingGuidelinerh
* Initial Upload Windows Compiling Guide
* Removed RIPEMD-160 from Product64.wxs. See commit from 21.03.2022
* Completed Win compiling guideline
* Added link to detailed compiling guide
* Added link to detailed compiling guide
* Restructured docu main page
* Added sourceforge link
* Added compiling guide for Linux
* References to detailed instructions
* Revert "Removed RIPEMD-160 from Product64.wxs. See commit from 21.03.2022"
This reverts commit 024ae2a465.
* Correction of a div box
* *: source files should not be executable
* *: make sure files have final newline
* *: remove BOM from text files
* translations: unify headers
* *: fix typos
* *: trim excess whitespace
* Start following IEEE 1541 agreed naming of bytes
This standard exists to prevent any confusion about the actual number of bytes. It has been agreed on by experts and is being used more widespead these day. Let's start properly naming the number of bytes, which is absolutely important in disk encryption software.
* Update LanguageStrings.cpp
* Update UserInterface.cpp
* kibibyte instead of kilobyte
* kibibyte instead of kilobyte
* MiB instead of MB
* undo accidental deletions
Odd indeed that two random lines were deleted in a previous commit. Probably happened when using a keyboard shortcut while editing the file. This fixes the issue.
* Mb to Mib
