WCX_RedTess - OCR (text recognition in TC)

[alexanderwdark]

Please compile the plugin with the option:
"Multithreaded (/MT)"
and not
"Multithreaded-DLL (/MD)".

This is misleading: The option does NOT mean that you want to create a DLL. It means that it uses the Microsoft redistribution package. When you use /MT option, then all necessary functions will be compiled into the plugin. Normally this doesn't make it much larger.

I can't build poppler's cairo lib as static because of glib (glib only supports dynamic library linkage)

[alexanderwdark]

18.10.2019 Now you can try static version of RedTess with no dlls. Both x86 and x86-64 versions on one archive

(build with patched poppler & glib)

[alexanderwdark]

2mikedepetris
please try latest version of plugin

[mrle]

Win7 (64-bit) + TotalCmd_v9.22a (32-bit) + redtess.wcx (32-bit):

---

"The program can't start because boost_date_time-vc141-mt-x32-1_70.dll is missing from your computer. Try reinstalling the program to fix this problem."

What could be the problem?

"boost_date_time-vc141-mt-x32-1_70.dll" is located in the "RedTess32" folder, with "redtess.wcx".

Registering DLL with "regsvr32.exe" didn't help.

^

This is with version from three days ago (from 15. okt).

---

And now, with this "static" version situation is even worse:

"The instruction at 0x61c0e187 referenced memory at 0x61c0e187. The memory could not be read."

[alexanderwdark]

2mrle
dll-based version was tested in Win7 by me, static - only in Win10, I'll see what could be there. The fact is that some libraries initially did not exist at all for statistical linking.

[Usher]

Of course the latest MSVC compiler supports XP (32-bit at least). It's been already explained that you should install xp toolset and properly configure it.

How can I compile/install libs in vcpkg using XP toolset?

1. You have already done one step - created static build, but it's only beginning.
2. The main problem is that installing v14*_xp toolset is not enough. It sets only minimal SUBSYSTEM version, but keeps default unchanged. As the linker uses default settings, you must set proper /SUBSYSTEM manually.
   See this discussion: https://stackoverflow.com/a/16088675

   The MSDN documentation for /ENTRY states that, if the /SUBSYSTEM argument is not specified that the SUBSYSTEM and ENTRY POINT are determined automatically.

3. There may be more settings required, see messages in a topic for another plugin:
   https://www.ghisler.ch/board/viewtopic.php?f=6&t=36578&p=349893&hilit=toolset%2A#p349893
   https://www.ghisler.ch/board/viewtopic.php?f=6&t=36578&p=349994&hilit=toolset%2A#p349994
   That plugin has been successfully compiled for Windows XP and works for me.

[mikedepetris]

2mikedepetris
please try latest version of plugin

Thank you, it is still giving me the same error.

[alexanderwdark]

2mikedepetris
please try latest version of plugin

Thank you, it is still giving me the same error.

Yes, If no ucrt libs in you system, it even will not work with static version. I don't know why some windows missing this lib. Because clean install of 7 or 10 has ucrt...

[alexanderwdark]

1. Now i installed clean win 10 1903 (business, msdn). Plugin in static version works even without any runtimes.

2. I have one win 10 when dependency walker or fileinfo from TC show problems also in kernell32, etc. for any software, inc. TC. Missing api-ms* libs
(this system was updated from win 8, i think)

So, this is some MS's bug. Look at AutoDesk QA - same pain with ucrt.

[alexanderwdark]

22.10.19 New build. Some fixes.

[Gral]

Still the same.

[alexanderwdark]

Still the same.

I managed to fix the problem system that I met only by reinstalling the OS to the latest version. Latest ISO from MSDN works ok, both win7 (sp1) and win10 (1903) in my VirtualBox (without need to install any runtime)

[alexanderwdark]

23.10.19 New build. You can get it here.

[Gral]

Still the same.

[Ovg]

Error: This is not a valid plugin!