Re: Compiling win32 source

[Jason D. <ja...@bb...>]

  > JD> I am insistant that the version they point you to download in the
> JD> building.txt is out of date.
> 
> No, BUILDING.txt should be ok, but the WinVNC.dsp file is damaged in
> the 1.2.9 distrbution. Corrected file is available separately from the
> download page.
>

Now when you say "Download page", I was looking over and over on the 
download page on tightvnc.com. Of course, I should have figured out 
where you meant, but WHAT GOOD does it do distributing the source on 
tightvnc.com when it is broken? There could AT LEAST be a link to the 
fixed .dsp there as well, but practically, the source package could just 
be repackaged.


> JD> Anyway, after the project was compiled, there was a DLL for
> JD> library project and the WinVNC.exe. With this, I am certain that
> JD> the code being distrbuted IS NOT the code used to build the
> JD> distributed binary. There are too many inconsistancies and
> JD> problems. The distributed package only has VNCHook.dll. The rest
> JD> are statically linked.
> 
> The 1.2.9 version was compiled using the Borland C++ 5.5 compiler. 
> Also, please note that 1.2.9 is not developed any more, so I'd
> recommend to try compiling 1.3dev5 instead. It's developed with Visual
> C++ 6.0.

Granted, but if I find Visual C++ project files in the source 
distribution, I would expect that they would work.

And a rule of thumb that most professionals follow... You NEVER use an 
unstable release in a production environment. I cant afford to trust the 
bleeding edge code, and I shouldnt have to.