-
Notifications
You must be signed in to change notification settings - Fork 24
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
Leptonica - Link Error #42
Comments
Oh, yes, sorry. Couple of paths were unfixed. |
No problem. Very appreciative of the work you are doing.
Everything worked great after upgrading.
…On Sun, May 17, 2020, 11:24 AM Egor Pugin ***@***.***> wrote:
Oh, yes, sorry. Couple of paths were unfixed.
sw --self-upgrade and try now. I've updated binaries.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#42 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA7VI3O7MNRW2CV2ZLIX3FTRSAFUPANCNFSM4NDOAEAA>
.
|
Egor, I'm also having linker issues with Tesseract as noted below. This may be a separate issue and I can open a new issue if you'd prefer, but it appears to be very similar. The simddetect.obj file causing the issue is located at: E:\src\repo\tesseract-master\win64\libtesseract.dir\Release, but Visual Studio is looking in E:\src\repo\tesseract-master\win64. If you need anything else please let me know. Severity Code Description Project File Line Suppression State E:\src\repo\tesseract-master\win64>sw --version On a side note when looking at the Additional Dependencies section in Visual Studio for my libtesseract project there were 14 duplicate entries. This likely has nothing to do with this linker issue and may not be a problem, but I thought I would point it out. |
Yes, I also observed that. Someone changed tess files without fixing tess build. I'll check. Upd.: this post is about build issue. |
|
I'll open an issue with the Tesseract group. Regarding the dependencies issue I was looking at the Additional Dependencies string under the Linker > Input options. I used Excel to split the string and sorted it which you can see below. When viewing through the Edit section the true duplicates are removed, but my screenshots below contain libs of the same name that are in different build folders; I don't see that in your screenshot. ADVAPI32.lib |
I see. |
See tesseract-ocr/tesseract#2986 about cmake error. |
Thanks Egor, sorry I didn't have a chance to look into this issue yesterday
or make a post.
…On Mon, May 18, 2020, 4:27 PM Egor Pugin ***@***.***> wrote:
See tesseract-ocr/tesseract#2986
<tesseract-ocr/tesseract#2986> about cmake
error.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#42 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA7VI3KNOZVMHLUQN7SNXJLRSGR2PANCNFSM4NDOAEAA>
.
|
Linking for Leptonica fails with the following error:
3>LINK : fatal error LNK1181: cannot open input file 'pkg\89\dc\64e7\obj\bld\144693\lib\org.sw.demo.gif-5.2.1.lib'
3>Done building project "leptonica.vcxproj" -- FAILED.
========== Build: 2 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
I'm building with Visual Studio 2017 and generated a solution file with the following command:
cmake -G "Visual Studio 15 2017 Win64" -DBUILD_SHARED_LIBS=1 -DSW_BUILD_SHARED_LIBS=0 ..
Of note the org.sw.demo.gif-5.2.1.lib file is located at: pkg\89\dc\64e7\obj\bld\469698\lib, but the lib folder, 144693\lib, in the link error does not exist. This also appears to be an issue with the other dependencies as the solution points to the 144693\lib folder, but the other lib files are also located in the associated 469698\lib folder.
If you need any other information please let me know.
Information:
E:\src\repo\leptonica-master\win64>sw --version
sw.client.sw version 1.0.0
git revision 3831e99
assembled on
17.05.2020 13:43:42 UTC
17.05.2020 08:43:42 Central Daylight Time
Windows 10 x64
The text was updated successfully, but these errors were encountered: