Ok so, i read how to properly report a BUG report and in my effort to
package a reproducible example with the symptom i faced, i did notice that
my module vcxproj file had a weird compiler option
<RuntimeTypeInfo>false</RuntimeTypeInfo>
After removing it everything works just fine with both release and debug
version of cryptopp. The proper way to set this through the node-gyp and
have a proper binding.gyp file is by having this
['OS=="win"', {
"msvs_settings": {
"VCCLCompilerTool": {
"AdditionalOptions": ["/GR"]
}
}
}]
I know that it may not interest you about electron native modules but i
think it would be a really time saver for someone that might face the same
issue and it would be nice if he could found that info somewhere.
Thank you for the immediate support, and once again thanks for this really
nice library
Cheers
Τη Παρασκευή, 21 Απριλίου 2017 - 5:24:40 μ.μ. UTC+3, ο χρήστης Jeffrey
Walton έγραψε:
>
>
>
>> I have pinpoint that the code that causes this problem is
>>
>> StringSource ss1(server_response, true, new StreamTransformationFilter(d,
>> new StringSink(recovered)));
>>
>>
>> Which is the cbc aes decryption code. If i comment out the above code
>> then the release version works as well.
>>
>
> What is the problem?
>
> Also see https://www.cryptopp.com/wiki/Bug_Report .
>
> Jeff
>
--
--
You received this message because you are subscribed to the "Crypto++ Users"
Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com.
More information about Crypto++ and this group is available at
http://www.cryptopp.com.
---
You received this message because you are subscribed to the Google Groups
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
