I had exact the same bugs. In my case the issue arises because I'm building
on x64 and thus have CRYPTOPP_X64_MASM_AVAILABLE set while
CRYPTOPP_BOOL_SSE2_ASM_AVAILABLE is not set.
In Visual Studio (at least 2015 upwards) this worked for me:
1. enable masm in *Build Dependencies* > *Build
On Sunday, December 17, 2017 at 10:51:20 AM UTC-5, MalleeswaraReddy s wrote:
>
> nasm -f elf64 -g -F dwarf -o x64dll.o x64dll.asm
>
> not able to compile
>
x64dll.asm provides the x64 ASM routines, but restricts to the functions
needed for the FIPS DLL; see
QMAKE_EXTRA_COMPILERS += nasm
NASMEXTRAFLAGS = -f elf64 -g -F dwarf
OTHER_FILES += $$NASM_SOURCES
nasm.output = ${QMAKE_FILE_BASE}.o
nasm.commands = nasm $$NASMEXTRAFLAGS -o ${QMAKE_FILE_BASE}.o
${QMAKE_FILE_NAME}
nasm.input = NASM_SOURCES
NASM_SOURCES += x64dll.asm \
nasm -f elf64 -g -F dwarf -o x64dll.o x64dll.asm
not able to compile
On Wednesday, December 6, 2017 at 1:26:08 AM UTC+5:30, Marcel Raad wrote:
>
> Am 30.11.2017 04:10 schrieb "MalleeswaraReddy s" >:
>
> cryptopp.lib(rijndael.obj) : error LNK2019: unresolved external
On Wednesday, November 29, 2017 at 10:10:45 PM UTC-5, MalleeswaraReddy s
wrote:
>
> On linux and mac , crypto cpp library with Qt worked correctlry.
>
> On windows msvc 2015 64 bit + Qt 5.9 getting error.
>
>
> --
On linux and mac , crypto cpp library with Qt worked correctlry.
On windows msvc 2015 64 bit + Qt 5.9 getting error.
--
"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN\nmake.exe" -f
Makefile.Release
On Wednesday, April 6, 2016 at 12:56:13 PM UTC-4, Freddy Martinez wrote:
>
> Hi guys... I have the cryptopp code inside my Qt Project and before I try
> to compile it with vs 2013, I always compile it with mingw and everything
> was fine. Now, I had download the Qt 5.5.1 version for vs 2013