Hello David, thanks a lot for this summary! It actually made the build much easier for me. Some more comments for people who work with OpenSuSE 12.3:
I also could only fetch fltk from here (svn is dead): http://fltk.org/pub/fltk/1.3.2/fltk-1.3.2-source.tar.gz I kept the threads enabled. And I didn't use any prefixes in the build to have everything in the standard path for convenience (no LD_LIBRARY_PATH needed). For building Xvnc one needs to install "xorg-x11-server" $ zypper install -t srcpackage xorg-x11-server and the source is then here: /usr/src/packages/SOURCES/xorg-server-1.13.2.tar.bz2 Compiling will still stop with vncExtInit.cc:1073:39: error: cast to pointer from integer of different size [-Werror=int-to-pointer-cast] The simple patch for that: cd ~/tigervnc-1.3.0/unix/xserver/hw/vnc perl -pi -e 's/-Werror=int-to-pointer-cast//' Makefile Thanks again, Michael On Fri, 1 Nov 2013, Dave Mackintosh wrote: > OK, I got it to build. > > Full notes are at > http://wiki.xdroop.com/space/Linux/TigerVNC/1.3.0/building+tigervnc > > Points that people perusing the mailing list might find useful if the above > page eventually falls off the internet: > > - don't use cmake for fltk > - fltk does not build shared libraries by default, to enable them you must > configure fltk with something like ./configure > --prefix=/usr/local/fltk/1.3.2-patched --enable-shared > - when building the server, I had to make a null Makefile in unix/xserver/man > because I didn't have the man source files for some reason > > The comment from Pierre about me doing a static build turned out to be the > hint I needed to get everything to work. > > I'm frustrated that the instructions for building fltk say to use cmake when > that doesn't work in my case. The fltk project seems to suggest that the > cmake infrastructure is not a supported/maintained mechanism and isn't to be > trusted. > > I'm also frustrated that the instructions don't explicitly tell you that this > build mechanism wants a shared library to link against, and doesn't tell you > to build the shared libraries. This could all be clearer, although I have no > idea how it affects builds on other platforms. > > All that said, I'm still pleased with TigerVNC, it is only because the server > I am using has a rpm dependency tangle that I can't use the EL6 rpms -- in my > testing, the EL6 rpms installed cleanly into a EL6 VM I was using. > > Thank you all for your assistance. > > -- > David Mackintosh > > ------------------------------------------------------------------------------ > Android is increasing in popularity, but the open development platform that > developers love is also attractive to malware creators. Download this white > paper to learn more about secure code signing practices that can help keep > Android apps secure. > http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk > _______________________________________________ > Tigervnc-users mailing list > Tigervnc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/tigervnc-users > ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ Tigervnc-users mailing list Tigervnc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-users
