On Wed, Dec 12, 2012 at 1:31 AM, Nathan Rajlich <[email protected]> wrote:
>> I am forced to wrap my header file for scrypt in `extern "c"` for correctly
>> linking. This is correct, isn't it?
>
> Not *totally* positive but I believe this is correct. Ben or someone
> else can probably clarify.
Yes, wrapping the include in an extern "C" { ... } block to force C
linkage is okay.
>> How can I ensure that the correct `SHA256_Update` is executed. And if this
>> is not being executed, what is?
>
> So this is kinda the tough problem right? Since you have control over
> the scrypt code at this point, you could rename that particular
> function since it seems to be incompatible with the SHA256_Update in
> the node binary. Again, one of the more experienced C guys can
> probably come up with a better solution for that particular problem.
If the functions have the same name but different prototypes, you'll
need to rename one (that's C for you - no namespaces).
You could apply linker magic to avoid the name clash but it's not very
portable. I'd recommend against it.
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" 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/nodejs?hl=en?hl=en
