public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Pavel Fedin <p.fedin@samsung.com>
To: 'Keith Seitz' <keiths@redhat.com>
Cc: insight@sourceware.org
Subject: RE: Building Insight for Cygwin
Date: Wed, 31 Jul 2013 05:54:00 -0000	[thread overview]
Message-ID: <002601ce8db2$6bb2ad10$43180730$%fedin@samsung.com> (raw)
In-Reply-To: <51F84A74.2010405@redhat.com>

 Hello!

> It's been a while since I tried this, so I'll give it a go.

 Here i also decided to try this.
 First, WinAPI version of TCL fails to build because of mentioned conflicts.
Additionally, AFAIK Cygwin may dislike when some app directly messes with
Winsock.
 In order to overcome all problems i decided to use a mix. Cygwin version of
TCL + WinAPI version of TK. This way the program will use Cygwin API for
everything except windowing. Should work well.
 Additionally i do it on 64-bit Cygwin. Had to apply some patchwork,
currently it almost builds. I will report results.
 If you are interested in patches, i could approve them here at Samsung for
submission. However, in this case my first wish: could you upgrade TCL and
TK in the repository to the recent version ? Current version is quite not
friendly to 64 bits, as well as exhibits serious bugs (app becomes
inresponsive in certain scenarios, i have a workaround for this).

 P.S. If some users want X11 inferface, while some others want native
interface, may be add configure's option ?

Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia



  reply	other threads:[~2013-07-31  5:54 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
2013-07-31  5:54   ` Pavel Fedin [this message]
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='002601ce8db2$6bb2ad10$43180730$%fedin@samsung.com' \
    --to=p.fedin@samsung.com \
    --cc=insight@sourceware.org \
    --cc=keiths@redhat.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).