From: Keith Seitz <keiths@redhat.com>
To: Pavel Fedin <p.fedin@samsung.com>
Cc: insight@sourceware.org
Subject: Re: Building Insight for Cygwin
Date: Tue, 30 Jul 2013 23:21:00 -0000 [thread overview]
Message-ID: <51F84A74.2010405@redhat.com> (raw)
In-Reply-To: <003801ce8c3f$9232bcb0$b6983610$%fedin@samsung.com>
On 07/29/2013 02:39 AM, Pavel Fedin wrote:
> How do i correctly build Insight for Cygwin ? I remember there were
> prebuilt binaries which used native Windows interface, not Cygwin's X11. How
> can i build this version ? Building TK/Win fails because of conflicting
> headers (e. g. sys/select.h and winsock2.h).
Insight uses a special version of Tcl/Tk which is checked into the
repository. That uses the native Windows APIs instead of X11. I know
that there are a quite a number of disgruntled Cygwin users who want
Insight to work via X11, though.
It's been a while since I tried this, so I'll give it a go.
Keith
next prev parent reply other threads:[~2013-07-30 23:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 9:40 Pavel Fedin
2013-07-30 23:21 ` Keith Seitz [this message]
2013-07-31 5:54 ` Pavel Fedin
2013-08-01 9:04 ` Pavel Fedin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51F84A74.2010405@redhat.com \
--to=keiths@redhat.com \
--cc=insight@sourceware.org \
--cc=p.fedin@samsung.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).