When I try to compile, encrypting debug info using the +encrypt_debug_info compiler flag, I get an error:
<filename>:none:error:this system is not configured with crypto support. I do have crypto installed in Erlware, so I checked sinan and the boot script shows that crypto isn't on its path. Other than messing with the boot script, which I really don't want to do, and assuming that my reasoning is sound, is there any other way I can get this compiler option to work? I don't want to strip out the debug code. Looking at the various issues that have come up because there is no SSL support in the Erlware toolset (three things come to mind: https WebDAV, Faxien signatures, and now this issue), can't you break down and insist on having OpenSSL available for Erlware? I mean, just about everything else that's secure in Open Source seems to require it. Or maybe just support it as an option by putting it in your toolchain's code path? -- You received this message because you are subscribed to the Google Groups "erlware-dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/erlware-dev?hl=en.
