Ok to commit? If so, this means that we will start building WinVNC (and
vncconfig.exe) during our automatic nightly builds.
I've committed the patch with minor modifications (changing TightVNC
Team to TigerVNC Team, expanding the description text in
CMakeLists.txt, and including MSVC in the
On Mon, 10 Oct 2011, Peter Åstrand wrote:
I mentioned it several times on the list, in the context of our
discussions regarding moving to CMake for Windows, regarding the
autotools performance problem on Windows, etc.
I've done a gmane search for libuuid on the tigervnc-devel list. No
So why didn't you report this? I cannot found anything about this,
neither in the tracker nor on the mailinglist. The patch apparently
worked fine for Adam and it worked fine for us.
I mentioned it several times on the list, in the context of our
discussions regarding moving to CMake for
For the record, I did try this 2 years ago, with the patch you and
Pierre submitted upstream to MinGW. It compiled but did not link.
So why didn't you report this? I cannot found anything about this, neither
in the tracker nor on the mailinglist. The patch apparently worked fine
for Adam
On 10/7/11 2:35 AM, Peter Åstrand wrote:
For the record, I did try this 2 years ago, with the patch you and
Pierre submitted upstream to MinGW. It compiled but did not link.
So why didn't you report this? I cannot found anything about this,
neither in the tracker nor on the mailinglist. The
On 10/4/11 4:34 AM, Peter Åstrand wrote:
Frankly, the fact that the main project developers insist on the use of
esoteric build environments is a problem.
MinGW had 1,059,337 downloads the last 7 days. The method of cross
compiling Windows binaries on Linux, using MinGW, is used by popular
On 10/6/11 2:50 AM, Peter Åstrand wrote:
Remind me, which functionality is missing if you build without Visual
Studio?
WinVNC. It's always been WinVNC.
It seems to me that instead of wasting time on maintaining multiple tool
chain, you could invest that time in streamlining the GCC based
On 10/6/11 2:50 AM, Peter Åstrand wrote:
Remind me, which functionality is missing if you build without Visual
Studio?
WinVNC. It's always been WinVNC.
Yes, but what is the problem with WinVNC? Nevermind, I looked back at the
discussions myself. It's the problem with IActiveDesktop missing
On 10/6/11 4:48 AM, Peter Åstrand wrote:
Yes, but what is the problem with WinVNC? Nevermind, I looked back at
the discussions myself. It's the problem with IActiveDesktop missing
from the MinGW distro.
IMHO, this is not unsolvable. If MinGW still refuses to add support for
this, we should
On Thu, 6 Oct 2011, DRC wrote:
IMHO, this is not unsolvable. If MinGW still refuses to add support for
this, we should be able to include the missing definitions in the
TigerVNC code base.
It's not just missing definitions. The patch you guys tried to commit
upstream didn't work, because it
Wow, Peter. So condescending. If I was in any mood to compromise
before, I'm certainly not now.
For the record, I did try this 2 years ago, with the patch you and
Pierre submitted upstream to MinGW. It compiled but did not link.
Well, curiously, apparently that patch made it into MinGW64, and
11 matches
Mail list logo
