-
Notifications
You must be signed in to change notification settings - Fork 742
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to compile and install 321-Tesseract-4 branch as a nuget package? #396
Comments
If you open the csproj in notepad does the path make sense?
…Sent from my iPad
On Mar 5, 2018, at 6:29 PM, masterisk <notifications@github.com<mailto:notifications@github.com>> wrote:
I have tried downloading the branch, opening in VS2015, and building the solution, as far as I can tell this just results in the Tesseract.dll.
Whenever I add the dll to a project as a reference, VS has a yellow triangle on the reference, and the path to the dll shows blank.
From the looks of the contents of the branch, there are nuget config files. How can I build the nuget package for Tesseract 4?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<https://protect-us.mimecast.com/s/2DQTCxk9r5f14wAjuvYzyB?domain=github.com>, or mute the thread<https://protect-us.mimecast.com/s/Hi-MCyPMv5FrzkM3SQdmrH?domain=github.com>.
|
It gives the path as a relative path. "............\Desktop\Tesseract\Tesseract.dll" |
Is that literal? It isn't a valid path. Fix the path with notepad.
On Mar 5, 2018, at 6:48 PM, masterisk <notifications@github.com<mailto:notifications@github.com>> wrote:
It gives the path as a relative path. "............\Desktop\Tesseract\Tesseract.dll"
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<https://protect-us.mimecast.com/s/Gz3DCYE09xcLJORPhGnt8b?domain=github.com>, or mute the thread<https://protect-us.mimecast.com/s/gTpkCZ6p9ys5V2ZyUKEkAS?domain=github.com>.
|
Sorry, there is a slash after every two dots. It’s navigating up a directory until it gets to the user account folder. Is a relative path still wrong? |
Relative paths are OK. As a test you could simplify the path and move the DLL somewhere easier to prove that the location is/isn’t the problem.
I just built 321 branch yesterday and had no problem.
|
It only seems to detect the reference if I have the dll directly in the project directory. Were you able to build the nuget nupkg? |
I haven’t tried.
|
I finally got it to work as a nuget package... it works without being in the project directory now. But I'm having another issue. I'm getting "Warning. Invalid resolution 0 dpi. Using 70 instead." I will close this thread and make another for the issue. |
I have tried downloading the branch, opening in VS2015, and building the solution, as far as I can tell this just results in the Tesseract.dll.
Whenever I add the dll to a project as a reference, VS has a yellow triangle on the reference, and the path to the dll shows blank.
From the looks of the contents of the branch, there are nuget config files. How can I build the nuget package for Tesseract 4?
The text was updated successfully, but these errors were encountered: