aboutsummaryrefslogtreecommitdiffstatshomepage
diff options
context:
space:
mode:
authorEgor Tensin <Egor.Tensin@gmail.com>2015-06-18 04:37:00 +0300
committerEgor Tensin <Egor.Tensin@gmail.com>2015-06-18 04:37:00 +0300
commitae96c012f876e477c6a7b1a0c0120bc4996f5688 (patch)
treea392d05cb295beabf380a90cf3710c2e8f10a730
parentbetter error messages + refactoring (diff)
downloadaes-tools-ae96c012f876e477c6a7b1a0c0120bc4996f5688.tar.gz
aes-tools-ae96c012f876e477c6a7b1a0c0120bc4996f5688.zip
README update
-rw-r--r--README.md10
1 files changed, 9 insertions, 1 deletions
diff --git a/README.md b/README.md
index 18deb3f..0612be6 100644
--- a/README.md
+++ b/README.md
@@ -8,13 +8,21 @@ I've used the compiler and the assembler shipped with Visual Studio Express 2013
You can generate the solution using CMake and build it using Visual Studio.
+Some of the utilities also depend on a few Boost libraries.
+In particular, Boost.ProgramOptions has to be built prior to building these utilities.
+To enable CMake to find Boost libraries, pass the path to the root Boost directory like this:
+
+ cmake -D BOOST_ROOT=C:\workspace\third-party\boost_1_58_0 ...
+
+Remember that in order to link to the static Boost libraries, you also have to pass `-D Boost_USE_STATIC_LIBS=ON` to CMake.
+
## Running on older CPUs
To run programs that are using the AES-NI instruction set on a CPU w/o the support for these instructions, one can use
[Intel Software Development Emulator](https://software.intel.com/en-us/articles/intel-software-development-emulator).
You can then run a program like this:
- > sde -- aes128ecb_encrypt_block.exe 000102030405060708090a0b0c0d0e0f 00112233445566778899aabbccddeeff
+ > sde -- encrypt_block_aes.exe -a aes128 -m ecb -- 000102030405060708090a0b0c0d0e0f 00112233445566778899aabbccddeeff
69c4e0d86a7b0430d8cdb78070b4c55a
## Documentation