Compiling VNCViewer statically [retry with attachment]

Jacob Hoover jacob.hoover@rbcmtg.com
Tue Jun 3 19:50:00 2003


Jessica,
   the list server automatically removes any attachments.  I haven't been 
following your posts, but if this is something you would like to share it 
would be nice if you could find a place on the web to store/serve it so 
that others may download it.

Jacob Hoover
At 11:50 AM 6/3/2003 -0600, Jessica Blank wrote:
>Woops. Forgot to attach the tarball. Here we go!
>
>On Tue, 3 Jun 2003, Jessica Blank wrote:
>
> > On Tue, 3 Jun 2003, Bill Cassady wrote:
> >
> > > On Mon, 2 Jun 2003, Jessica Blank wrote:
> > >
> > > > Date: Mon, 2 Jun 2003 22:40:29 -0600 (MDT)
> > >
> > > > Hi! OK, so now I've finally compiled RealVNC under Mac OS X.
> > >
> > > Gee, it sure would be nice if you told list members how you finally
> > > managed to do that. It might save someone else some
> > > trouble/inquiries/responses...
> >
> > Read back, there's a whole thread on the list about this :)
> >
> > Attached is a little tarball, it's not really a "patch"... just untar it
> > into the "vncviewer" source dir and compile as usual. All it basically
> > does is remove one level of macro expansion. Instead of making GET_PIXEL a
> > pointer (or whatever) to GET_PIXEL_8, GET_PIXEL_16 and GET_PIXEL_32, one
> > inserts the text of GET_PIXEL_(8|16|32) directly into three separate
> > versions of hextile.c (hextile8.c, hextile16.c, hextile32.c) and modifies
> > rfbproto.c accordingly...
> >
> > >
> > > ...before you request more assistance.
> > >
> > > -Bill
> > >
> > > > ...now, how can I compile it STATICALLY, so I can distribute it to 
> others
> > > > without having to worry if they are tech-savvy enough to install 
> whatever
> > > > libs are needed?
> > > >
> > > > I've tried all sorts of muckety-mucking about with the various *FLAGS
> > > > variables in configure.in and in the Makefiles... I cannot produce a
> > > > static vncviewer binary.
> > > >
> > > > Can someone help me please?
> > > >
> > > > And please, no lectures on why static linking is a Bad Thing. I've 
> heard
> > > > it a trillion times. But try telling that to the newbie who says
> > > > "durrrrrh, it no worky", and when you get them to run it from the shell
> > > > (if you can talk them through that much), they say "durrrrrh, it say
> > > > somefin' about libFOO dot ess-oh dot ... durrrrh, what id dat?"...
> > > >
> > > > Sorry, sometimes it's worth it to statically link. Like when releasing
> > > > something to the public. I love it when projects offer BOTH static and
> > > > dynamic binaries...
> > > >
> > > > Anyhow. Can someone help me? Again, please, no lectures.
> > > >
> > > > J e s s i c a    L e a h    B l a n k
> > >
> > >
> > > caersidi@sdf.lonestar.org
> > > SDF Public Access UNIX System - http://sdf.lonestar.org
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > ;)
> > > _______________________________________________
> > > VNC-List mailing list
> > > VNC-List@realvnc.com
> > > To remove yourself from the list visit:
> > > http://www.realvnc.com/mailman/listinfo/vnc-list
> > >
> >
> > J e s s i c a    L e a h    B l a n k
> >
> > [demime 0.99d.1 removed an attachment of type APPLICATION/x-gzip which 
> had a name of vncviewer-3.3.7-macosx-patch.tar.gz]
> > _______________________________________________
> > VNC-List mailing list
> > VNC-List@realvnc.com
> > To remove yourself from the list visit:
> > http://www.realvnc.com/mailman/listinfo/vnc-list
> >
>
>J e s s i c a    L e a h    B l a n k
>
>[demime 0.99d.1 removed an attachment of type APPLICATION/x-gzip which had 
>a name of vncviewer-3.3.7-macosx-patch.tar.gz]
>_______________________________________________
>VNC-List mailing list
>VNC-List@realvnc.com
>To remove yourself from the list visit:
>http://www.realvnc.com/mailman/listinfo/vnc-list