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
When creating the build tool, I made the decision to retain the build products between builds to speed up the build process while in the development process. It’s possible that there are binaries left over from the version of Visual Studio you were running before installing Visual Studio 2019.
For example, in your full build log, I notice there is a link error associated with tessdatamanager.obj. But I don’t see the corresponding compiler command. This leads me to believe tessdatamanager.obj binary might have been built with an earlier version of Visual Studio which could explain the linking error.
As a first step, I recommend that you try this command to clean out the build products:
npm run clean-tesseract
And then try the:
npm install
stoefln
changed the title
Installing in Windows 11 leads to error
Windows 11 fatal error: LNK1120: 1 unresolved externals [C:\...\node_modules\node-native-ocr\build\node-native-ocr.vcxproj
May 12, 2022
node -v v14.18.1
node-gyp -v v5.1.0
Full log:
https://gist.github.com/stoefln/fa6fbe2975ea9f85d7e221124f23ef13
The text was updated successfully, but these errors were encountered: