I personally looked into that, in the context of supporting Red Hat Enterprise 6. It was my opinion that the procedure is too system-specific to go in BUILDING.txt. In order to get a version of Xvnc that actually works, you have to specify other things, such as the font path, etc. It is simply not something that we have the cycles to support. People will read BUILDING.txt and try to literally follow the procedure, and this will only lead to confusion.
I think our wiki is the appropriate place to maintain system-specific build procedures for various platforms. On 8/2/11 11:13 AM, Marc Weber wrote: > Hi dev team, > > It would be helpful if the BUILDING.txt file provides a starting point > to build non legacy Xvnc. > > The attached patch illustrates what I have in mind. > > Those steps work for me. > > Marc Weber ------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
