The build system in TigerVNC unfortunately seems to require autoconf
2.61 or higher and also a later version of automake than is available on
even the latest Enterprise Linux system (CentOS 5.2.) Thus, I cannot
build the software, nor can anyone else running Enterprise Linux. I
would suggest checking the configure script into the SVN repository.
The RealVNC source code does this. It will give advanced users the
option to chance the autoconf files as they see fit but will not require
the use of autoconf/automake for the more mundane builds of the software.
Yes, I know I could install an updated version of autoconf and probably
make it work. My point is that that is too much to ask of the average
developer. TigerVNC must be as easy to build as RealVNC.
Perhaps. On the other hand, I think we can ask a little bit more of
developers than average users/installers. I've not tested how hard it is
to upgrade Autoconf on an 5.2 system, but perhaps it's fairly straight
forward? In that case, perhaps it would be sufficient to document this?
Releases will of course contain configure scripts and Makefile.in:s.
That said, I can live with checked in configure scripts and
Makefiles.in:s.
Regards,
---
Peter Åstrand ThinLinc Chief Developer
Cendio AB http://www.cendio.com
Wallenbergs gata 4
583 30 Linköping Phone: +46-13-21 46 00
------------------------------------------------------------------------------
_______________________________________________
Tigervnc-devel mailing list
Tigervnc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
