Cendio is going to finance the project, so I will be beginning work on
the new CMake build system within the next week. I need to do some
investigation first to get a feel for how to do cross-compilation, host
detection, feature checking, and other things that will eventually be
necessary
On Tue, 5 Oct 2010 16:58:07 +0200
Adam Tkac at...@redhat.com wrote:
In my opinion we should consider to use CMake instead of GNU build
chain as our primary build system in 1.1. If I understand correctly
Darrell is also for CMake but I would like to hear opinion of Peter
and Pierre.
We
I agree. SourceForge has mediawiki pre-installed, so projects such as
ours can choose to use that for our web site instead of a static page.
On 10/1/10 11:30 AM, Antoine Martin wrote:
I think that things like this deserve to go on a wiki somewhere... it
would make them much more accessible
I'm not sure if a clickable app is the right approach. The vncviewer
code is a Unix/X application that communicates important information via
the command line, so as a clickable app, there would be no way for it to
communicate errors to the user. It would simply die silently if, say,
the X11 app
On Fri, Oct 01, 2010 at 02:38:53PM -0500, DRC wrote:
I agree. SourceForge has mediawiki pre-installed, so projects such as
ours can choose to use that for our web site instead of a static page.
Last time I looked at mediawiki offered by SoureForge, edit rights
must be granted by the wiki admin
I see that as a feature, not a bug. We don't want it to be a
free-for-all. We want access controls similar to the subversion repository.
On 10/1/10 4:44 PM, Martin Koegler wrote:
On Fri, Oct 01, 2010 at 02:38:53PM -0500, DRC wrote:
I agree. SourceForge has mediawiki pre-installed, so
The Xorg 7.5 code base is known not to work on older systems (RHEL 4 and
5, in particular) due to an autotools incompatibility (even though the
configure.ac file in Xorg says it supports AC 2.57 and later, it uses
some macros that are only available on newer versions.) However, it
should work on
I've been getting my hands dirty with CMake in recent weeks, and I now
firmly believe that's the way to go with respect to a Windows build
system for TigerVNC. I don't propose replacing autotools (at least for
now), but CMake allows one to generate their own build system based on
NMake or Visual
I would be glad to see a better cross platform build system. I have
done some work with CMake in the past and with SCons. I found Scons to
be a better system overall. One of the big selling points of it for me
was that it literally replaced the native systems make command and
launched the
I didn't say that SCons didn't work great on Windows. I just said that
it was my impression that CMake was more Windows-friendly. By that, I
mean it has full support for generating IDE projects and doesn't require
external dependencies like Python, etc. I thought the link from the
SCons wiki
On Thu, Sep 16, 2010 at 03:14:02AM -0500, DRC wrote:
Once I can successfully get a static build going on RHEL 4 (still having
problems with the lack of gnutls_transport_set_global_errno), I'll look
into these issues. libgcrypt and libgnutls are definitely not
cross-compatible, so the -static
On 9/16/10 4:15 AM, Adam Tkac wrote:
My MinGW patch isn't accepted, yet. And I'm not sure if it will be
accepted:
https://sourceforge.net/mailarchive/message.php?msg_name=AANLkTikg0hAGpArLTqFSWn6IdSI5aNOwJk-3ZDl4rqrq%40mail.gmail.com
I'm going to merge my vcstudio_buildsys branch to trunk so
12 matches
Mail list logo
