On 8/17/11 4:01 PM, Martin Koegler wrote: > First of all, Makefile.am is missing some include path, so that a out of > source tree build fails (xserver 1.7): > --- tigervnc-1.0.1.svn0.orig/unix/xserver/hw/vnc/Makefile.am > +++ tigervnc-1.0.1.svn0/unix/xserver/hw/vnc/Makefile.am > @@ -17,7 +17,8 @@ libvnccommon_la_SOURCES = $(HDRS) vncExt > > libvnccommon_la_CPPFLAGS = -DVENDOR_RELEASE="$(VENDOR_RELEASE)" \ > -DVENDOR_STRING="\"$(VENDOR_STRING)\"" -I$(TIGERVNC_SRCDIR)/common > -UHAVE_CONFIG_H \ > - -I$(TIGERVNC_SRCDIR)/unix/vncconfig $(XVNC_CPPFLAGS) > -I$(includedir)/pixman-1 -I$(includedir) > + -I$(TIGERVNC_SRCDIR)/unix/vncconfig $(XVNC_CPPFLAGS) > -I$(includedir)/pixman-1 -I$(includedir) \ > + -I$(top_srcdir)/include > > bin_PROGRAMS = Xvnc > > @@ -49,6 +50,7 @@ libvnc_la_CPPFLAGS = $(XVNC_CPPFLAGS) -I > -I$(top_srcdir)/hw/xfree86/common \ > -I$(top_srcdir)/hw/xfree86/os-support \ > -I$(top_srcdir)/hw/xfree86/os-support/bus \ > + -I$(top_srcdir)/include \ > -I$(includedir)/pixman-1 -I$(includedir) > > libvnc_la_LDFLAGS = -module -avoid-version > > My second problem is, that it seems no longer possible to build the vnc > module. Linking the > vnc module for the Xserver leads to an linker error, because cmake only > generates non-PIC object files (eg libnetwork). > autotools+libtool did this automatically.
How are you trying to build the module? I honestly only ever use build-xorg, which automatically adds the -fPIC flag, but I understand that a different procedure is required on more modern systems. ------------------------------------------------------------------------------ Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
