From: Pavel Fedin <p.fedin@samsung.com>
To: 'Roland Schwingel' <roland@onevision.com>, insight@sourceware.org
Subject: RE: Bundled TCL/TK - update needed
Date: Tue, 21 Jan 2014 12:36:00 -0000 [thread overview]
Message-ID: <003801cf16a5$720b93d0$5622bb70$%fedin@samsung.com> (raw)
In-Reply-To: <52DE6150.5040102@onevision.com>
Hello!
> AFAIK Tcl/tk 8.4 is out of service. I wanted to update the intree
> versions to 8.6 some time ago, but I was shifted away to do other
> projects after I did the initial porting of insight to 64bit windows.
Would be nice if you do it. I think it should not take lots of time. Just
checkout and import.
Actually in my case 8.4 works fine enough on Win7 64bit, but with some
patches.
> I haven't built a cygwin version of insight for a long time. I am
> mainly using insight on mingw64 - where it runs very good as I am
> debugging mainly mingw64 code.
Yes, MinGW version is better, but there is one thing. Actually my target is
an embedded ARM Linux system, and it's quite hard to use MinGW. For example,
in order to generate SquashFS images correctly, build libraries, etc, i need
support for symlinks. This is why i stick to Cygwin. And MinGW software
doesn't read Cygwin symlinks, so it is not easy to use "set sysroot" in
Insight.
I could try building Cygwin version myself, however first TCL update is
needed because i don't want to carry on all that patches. This is why i'm
asking for TCL update.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
next prev parent reply other threads:[~2014-01-21 12:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 12:00 Roland Schwingel
2014-01-21 12:36 ` Pavel Fedin [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-01-21 11:33 Pavel Fedin
2014-01-21 15:23 ` Tom Tromey
2014-01-27 7:25 ` Pavel Fedin
2014-01-27 21:32 ` Keith Seitz
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='003801cf16a5$720b93d0$5622bb70$%fedin@samsung.com' \
--to=p.fedin@samsung.com \
--cc=insight@sourceware.org \
--cc=roland@onevision.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).