Hello,

>>>>> "so" == "some one" <[EMAIL PROTECTED]> writes:

so> I have some questions about compliling TightVNC source files. When
so> using the downloadable source files the winvnce.exe that is
so> created (when Release is chosen) is larger in size than that which
so> is installed using the TightVNC install package, about 50kb
so> larger.

so> Also, to run the install package version of winvnc.exe, the only
so> other file required is VNCHooks.dll.

so> When I compile the source files I need to compile VNCHooks.dll,
so> zlib.dll and omnithread_rt.dll as well in order to ger WinVNC to
so> run.

so> In the build doco it says that you should build the No_Corba
so> version. How do you do that? I could not find this as an option. 
so> All I can find is Release, Debug, Profile and HorizonLive.

so> Am I missing something really basic here? I am a real newbie to
so> C++ so be kind, please. :-)

All the TightVNC releases were compiled using Borland C++ compiler. 
That's the reason for such differences. There are corresponding
compilation notes in the file BUILDING-bcc32.txt, within the source
distribution.

If you would like to compile TightVNC with MS VC++ 6.0, and don't want
libraries to compile into DLLs, use the latest sources from the CVS
tree -- we have fixed that issue recently.

As for the No_Corba configuration, it is obsolete. I'll fix the
winvnc/BUILDING.txt file to reflect that fact.

-- 
With Best Wishes,
Constantin
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Reply via email to