Straw poll - VC++6 vs VC++ Express about tesseract-ocr HOT 14 CLOSED

Since some will have VC++6 whereas others may have VC++ express(appears new
version?). IF so,generally majority will have old version of VC++6. 
However it is felt that there is no harm to have format files of both versions 
viz.,
VC++6 and VC++express.
For this purpose two folders viz (1) VC++6(containing dsp, dsw) and
(2)VC++express(containing dsp, dsw) have to be created. 
At the time of compilation, say VC++6, then copy contents of folder VC++6 and 
pasted
under main directory and then recompiled with help of VC++6 as usual.

It would be more appropriate to create zip files viz(1) "dsp,dsw of VC+6.zip" 
and 
(2) "dsp,dsw of VC++Express.zp" and "readme dsp,dsw".  

Just to clarify what I meant here:

v2.00 is going to include a set of .dsp and a .dsw file for VC++6.
It will also include (for the first time) a set of .vcproj and a .sln file for 
VC++
express.
Although I am no fan of the changes made between vc++ 6 and 7, the newer 
versions do
support a more standard compiler, and vc++ express is free, so it is available 
for
anyone to use.
At some point in the future, support for VC++6 is going to get dropped because 
it is
going to be too hard to support, along with everything else.

So if there are any ardent vc++6 fans out there that are not going to give up 
VC++6
at any time in the near future, would they please squeal now so they can be
identified and conned into continuing the support of the old version...

Good idea.
It is presumed that 
(1) a proposed set of .vcpro will contain: .dsp plus .dsw files for "VC++6" 
software.
whereas 
(a) set of .sin   will contain: .dsp plus .dsw files for "VC++2005 
expressdition" 
software

Regarding VC++ express is free: after 30days, whether it will cease to run, in 
case
if failed to registered. Kindly confirm whether VC++express is 
"VisualC++ 2005-Express Edition".  Since VC++ express (i.e.Visual C++
2005-ExpressEdition)is new to me, as such I seek clarification.

I actually use VC++5, and based on the current .dsw I can get things
compiled after a few minor changes to fix errors about redefinitions,
by commenting out

//typedef SIGNED char INT8;
//typedef SIGNED char *PINT8;

and to fix illegal use of long long, commenting out

//typedef long long int INT64;
//typedef unsigned long long int UINT64;

and deleting a precompiled header file.

I would certainly "squeal" if it would become harder to get
tesseract compiled under VC5, which I do not plan to replace
in the foreseeable future. Buying a new professional version 
as required for legal distribution of binaries is expensive.

> So if there are any ardent vc++6 fans out there that are not going to give up 
VC++6
> at any time in the near future, would they please squeal now so they can be
> identified and conned into continuing the support of the old version...

2.04 is likely to be the last version that can be built under vc++6. There is a 
lot 
of new code coming in 3.00 that may not compile easily under vc++6.

I am having troubles compiling under VC++ Express 2008.  Any advise?
I need also to compile with tiflib so I can use it with compressed tif images.
Thanks,

Try downloading the latest source from svn. There is an alpha version of 2.04 
up 
there that is not yet ready to release as tar.gz, but it might compile better 
on vc++ 
express 2008. If not, let me know what the problems are.
Ray.

Ray,
Thank you.  I got latest version, try to compile but I get 2 errors and 235 
warnings
Error C3861: 'sscanf': identifier not found

Warning 1   warning C4996: 'strcpy': This function or variable may be unsafe. 
Consider using strcpy_s instead

Warning 2   warning C4305: 'initializing' : truncation from 'int' to 'float'
All the warnings pretty much the same message..

Sincerely,
Alex

xvxcv

I have installed Visual Studio dot net 2008 express edition. I fail to compile 
tesseract 2.03.

i'm successfully compiling 2.04 and r379 with VS2008.
However, if i want to set-up a personal project using the API DLL, it's a 
problem since a lot of headers are 
required for it to compile... There is no point then to export an exposed API.

VC++6 is no longer useable in 3.00, since it can't compile the code anymore.
3.00/3.01 will migrate to VC++ express 2008/2010.