You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
jnidng.cpp(27414): error C2664: 'SharedPtrAdapter<dng_memory_block>::SharedPtrAdapter(const std::shared_ptr<dng_memory_block> &)': cannot convert argument 1 from 'std::shared_ptr<const dng_memory_block>' to 'const std::shared_ptr<dng_memory_block> &'
jnidng.cpp(27414): note: Reason: cannot convert from 'std::shared_ptr<const dng_memory_block>' to 'const std::shared_ptr<dng_memory_block>'
jnidng.cpp(27414): note: No user-defined-conversion operator available that can perform this conversion, or the operator cannot be called
This line seems to be the problem child SharedPtrAdapter< const dng_memory_block > radapter(ptr->fSemanticXMP);
It makes sense, since the generic types don't match. Is there an easy way to overcome this using InfoMap (such as javaText(...) ) or is this just one of them issues where I gotta do something jank to overcome? I poked around in some of the other bindings but couldn't find an analogous case.
FYI I'm using 1.5.9 right now because I can't upgrade my CUDA yet. So if this is a bug that has already been fixed by the generator then I'll wait till we upgrade.
The text was updated successfully, but these errors were encountered:
Working on some presets for the Adobe DNG SDK, and I'm down to the final error.
I'm running into a compilation problem with setter func in the jni file from this definition (only showing relevant line):
Javacpp is generating the following output:
Here is the error I receive:
This line seems to be the problem child
SharedPtrAdapter< const dng_memory_block > radapter(ptr->fSemanticXMP);
It makes sense, since the generic types don't match. Is there an easy way to overcome this using InfoMap (such as javaText(...) ) or is this just one of them issues where I gotta do something jank to overcome? I poked around in some of the other bindings but couldn't find an analogous case.
FYI I'm using 1.5.9 right now because I can't upgrade my CUDA yet. So if this is a bug that has already been fixed by the generator then I'll wait till we upgrade.
The text was updated successfully, but these errors were encountered: