Hi. Let me rephrase myself.

I want to compile the RealVNC VNC viewer on Mac OS X. I do not wish to use
VNCThing. I do not wish to use Chicken of the VNC. (Though thanks to the
very kindly list member who pointed out its existence to me.) I just want
to keep using the same old trusty VNC sources that have worked for me
for years. I was using VNC before it was called RealVNC. I was
using VNC before ORL got bought out by AT&T. I was using VNC before anyone
had even heard of it; I wish to keep using VNC (and not some
little-known spinoff). No offense to the spinoff writers-- you do valuable
work. I JUST WANT MY PLAIN OLD REALVNC, thanks!

VNCThing is not fast enough-- it's ancient and has not been updated in God
knows how long.

Chicken of the VNC is a nice stopgap solution, but it's derived from a
third-party OpenStep project, not from original VNC project sources... and
hence it has some interoperability issues with servers based on the 'real'
VNC tree:

1) 16-color mode is rendered as some funky sort of monochrome. The first
time I connected to my 16-color server at work, it came out all in shades
of green. The second time I connected to that same server, it was red!

2) It doesn't seem as fast.

3) Did I mention it doesn't seem as fast?

4) I just want to use the real RealVNC sources. Color me silly, but I
don't like depending on obscure third-party solutions when something that
SHOULD compile perfectly fine (but doesn't) is available). THREE STINKING
SYMBOLS are presenting it from compiling...

Again, the error I encountered in building xvncviewer is below:

> The build goes smoothly until the laaaaaaast line, when I see:
>
> ---------------------------------------------------------------------
> rm -f vncviewer
> c++ -O2 -Wall  -o vncviewer argsresources.o colour.o desktop.o dialogs.o
> fullscreen.o listen.o misc.o popup.o rfbproto.o selection.o shm.o
> vncviewer.o sockets.o zrle.o buildtime.o ../rfb/librfb.a ../rdr/librdr.a
> ../zlib/libz.a  -lSM -lICE  -L/usr/X11R6/lib -lXmu -lXaw -lXt -lX11 -lXext
> ld: Undefined symbols:
> _GET_PIXEL16
> _GET_PIXEL32
> _GET_PIXEL8
> make: *** [vncviewer] Error 1
> sh-2.05a#
> ---------------------------------------------------------------------

Again, this is using OS X 10.2.6 (Jaguar, latest) with the December 2002
Jaguar Development Tools package installed. I am running the Apple X11
port (beta 3 I believe), including Apple's SDK and Apple's X11 server. The
C compiler is Apple's fork of GCC, build 1175, based on GCC 3.1 dated
4/20/2002... as you can see below:

> ---------------------------------------------------------------------
> bash-2.05a$ gcc -v
> Reading specs from /usr/libexec/gcc/darwin/ppc/3.1/specs
> Thread model: posix
> Apple Computer, Inc. GCC version 1175, based on gcc version 3.1 20020420
> (prerelease)
> bash-2.05a$ cc -v
> Reading specs from /usr/libexec/gcc/darwin/ppc/3.1/specs
> Thread model: posix
> Apple Computer, Inc. GCC version 1175, based on gcc version 3.1 20020420
> (prerelease)
> bash-2.05a$ g++ -v
> Reading specs from /usr/libexec/gcc/darwin/ppc/3.1/specs
> Thread model: posix
> Apple Computer, Inc. GCC version 1175, based on gcc version 3.1 20020420
> (prerelease)
> bash-2.05a$ c++ -v
> Reading specs from /usr/libexec/gcc/darwin/ppc/3.1/specs
> Thread model: posix
> Apple Computer, Inc. GCC version 1175, based on gcc version 3.1 20020420
> (prerelease)
> bash-2.05a$
> ---------------------------------------------------------------------

Again, I have tried all sorts of weird things to get this build to work,
including going so far as to copy the entire #defines for GET_PIXEL16,
GET_PIXEL32 and GET_PIXEL8 into a file called "libstupidmac.c" and
compiling it, then adding "libstupidmac.o" to the end of the link line, as
my way of force-feeding the symbols down the linker's throat.

Again, It made no difference. Same error messages. It was as if I'd done
nothing at all.

Please, please, please, please, please could someone wiser than myself
HELP ME? I see no reason why a comparatively simple X11 application like
the VNC viewer, with no GTK or QT dependencies, no use of funky libraries,
and essentially no GUI at all, should not be easily portable to Mac OS X
running X11! I'm not asking for some fancy Aquafied interface here. I just
want to port plain old vanilla XVNCViewer... why is this so difficult?
PLEASE, someone just assist me.

Am I some sort of heretic for just wanting a solution to a simple problem
that shouldn't exist at all, as far as my feeble mind can see?
>

J e s s i c a    L e a h    B l a n k
_______________________________________________
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