Etienne Cimon

The forward slash works, I noticed it also takes the path of the `libs-dirs` with native slash ` lib-dirs = [ "A:\development\d_android/runtime_droid_x86", ];`

Everything being fixed, this is where it fails for me: ``` PS A:\development\memutils> dub test --arch=armv7a-none-linux-android Failed to apply the selected architecture armv7a-none-linux-android. Got ["arm"]. Generating test runner configuration 'memutils-test-unittest'...

I think it should be calling `clang++.exe` on Windows according to the cmd. files under the same path

The full path would have to be `C:/Users/PC/AppData/Local/Android/Sdk/ndk/21.0.6113669/toolchains/llvm/prebuilt/windows-x86_64/bin/clang++ --target=armv7a-linux-androideabi21` but I don't know how to pass that as an `-gcc=` switch

``` Linking... Error: 'C:/Users/PC/AppData/Local/Android/Sdk/ndk/21.0.6113669/toolchains/llvm/prebuilt/windows-x86_64/bin/clang --target=armv7a-linux-androideabi21' failed with status: -1 Error: message: program not executable ```

``` clang: error: linker command failed with exit code 1 (use -v to see invocation) Error: C:/Users/PC/AppData/Local/Android/Sdk/ndk/21.0.6113669/toolchains/llvm/prebuilt/windows-x86_64/bin/armv7a-linux-androideabi21-clang.cmd failed with status: 1 C:\D\ldc2\bin\ldc2.exe failed with exit code 1. ```

There should be some kind of `-CFLAGS=` argument so that `-gcc` can stay the path of an executable and so that I can set `--target=...` for it

Using clang++.exe without a flag, I also needed to use "-linker=C:/Users/PC/AppData/Local/Android/Sdk/ndk/21.0.6113669/toolchains/llvm/prebuilt/windows-x86_64/bin/arm-linux-androideabi-ld.exe",` and then I'm stuck on: ``` C:/Users/PC/AppData/Local/Android/Sdk/ndk/21.0.6113669/toolchains/llvm/prebuilt/windows-x86_64/bin/arm-linux-androideabi-ld.exe: error: cannot open crt2.o: No such file or directory C:/Users/PC/AppData/Local/Android/Sdk/ndk/21.0.6113669/toolchains/llvm/prebuilt/windows-x86_64/bin/arm-linux-androideabi-ld.exe: error: cannot...

You should also make sure you call `.destroy` on your AES object to zeroise your key from memory as its destructor intends. You can also place it in a `Unique!AES256`....

Sorry, that's `retrieveBlockCipher` from `import botan.libstate.lookup`