Add MSBuild targets for net46 target framework which copy both x86 and
x64 libsodium binaries into corresponding folders. This allows AnyCPU
applications to load the appropriate binary at runtime via
`LoadLibraryEx`.
The `which` command is not part of the posix standard and not available
in some environments. The `command` command is part of the posix
standard and well supported.
See https://unix.stackexchange.com/q/85249 for a discussion about the
use of `command` instead of `which`.
If a system had `libtool` but not `which`, the build process would issue
an erroneous error stating:
libtool is required, but wasn't found on this system
Switching to `command` corrects this problem.
* 'master' of github.com:jedisct1/libsodium:
Fix `crypto_pwhash_argon2i_str_verify()` and its tests after `errno` changes
Add crypto_pwhash_MISMATCH errno (#541)
* Use intermediate variables in slide() which removes ambiguity for the compiler and fixes a crash in the PPC_VLE build with -O1 flag (added bonus: smaller compiled code.)
* Fix formatting in slide() loop counter to match the previously just-formatted version.
* Fix invalid stream of Visual Studio DynDebug build logs.
* Remove ARM props file (undergeneralized).
* Clean up white space in Visual Studio *.props files.
This reverts commit 87c408b42d.
CL.exe doesn't seem to be in the path any more when using the
AppVeyor Visual Studio 2017 environment.
msbuild "C:\projects\libsodium\libsodium.vcxproj" /m /verbosity:minimal /logger:"C:\Program Files\AppVeyor\BuildAgent\Appveyor.MSBuildLogger.dll"
Microsoft (R) Build Engine version 15.1.548.43366
Copyright (C) Microsoft Corporation. All rights reserved.
TRACKER : error TRK0005: Failed to locate: "CL.exe". The system cannot find the file specified. [C:\projects\libsodium\libsodium.vcxproj]
