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
Similar to the above, a CUDA based build also produces a libopencv_cudaobjdetect.so (or platform specific equivalent), which will cause the resulting opencv4nodejs module to fail to load at runtime (due to node-gyp missing symbol shenanigans, it builds just fine without the right libraries linked).
For now, it looks like another dirty hack of .filter(file => !file.includes('cuda')) is sufficient to get the right libraries linked. However, these hacks are a byproduct of a flawed approach to how you find the libraries in the first place. I've put more details along with a suggestion here: justadudewhohacks/opencv4nodejs#162 (the issue that I actually encountered)
This is not a request to actually support CUDA-based modules, just that their presence doesn't cause the module to fail to load.
The text was updated successfully, but these errors were encountered:
npm-opencv-build/libs.js
Line 44 in 1228a60
Similar to the above, a CUDA based build also produces a
libopencv_cudaobjdetect.so
(or platform specific equivalent), which will cause the resulting opencv4nodejs module to fail to load at runtime (due to node-gyp missing symbol shenanigans, it builds just fine without the right libraries linked).For now, it looks like another dirty hack of
.filter(file => !file.includes('cuda'))
is sufficient to get the right libraries linked. However, these hacks are a byproduct of a flawed approach to how you find the libraries in the first place. I've put more details along with a suggestion here: justadudewhohacks/opencv4nodejs#162 (the issue that I actually encountered)This is not a request to actually support CUDA-based modules, just that their presence doesn't cause the module to fail to load.
The text was updated successfully, but these errors were encountered: