From: Michael Richardson <mcr@solidum.com>
To: gnu-win32@cygnus.com
Cc: thai@venus.solidum.com, feliks@venus.solidum.com
Subject: experience with TCL/TK with CygWin32
Date: Thu, 15 Oct 1998 00:44:00 -0000 [thread overview]
Message-ID: <199810141740.NAA03024@venus.solidum.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
The libtcl.a and libtk.a files are present in the CygWin tree. I'm
just wondering if there are people who have experience with these, and
if you have had any problems? We did not realize that it was already there,
and started trying to figure out how we were going to build the stuff in
tcl8.0.3/win with CygWin.
More to the point: is it possible to simply link the Win32 distribution of
TCL/TK (which comes in DLL form) to our Cygwin application.
We will need to upgrade to 8.0.3. (b19 has 8.0.2).
From looking at my build of b19 (as a cross compiler) it appears that
CygWin has built the *unix* version of Tcl under CygWin32. I am suspicious
that this means that Tk has been built against X11 rather than Win32 GDK.
:!mcr!: | Solidum Systems Corporation, http://www.solidum.com
Michael Richardson |For a better connected world,where data flows faster<tm>
Personal: <A HREF=" http://www.sandelman.ottawa.on.ca/People/Michael_Richardson/Bio.html ">mcr@sandelman.ottawa.on.ca</A>. PGP key available.
Corporate: <A HREF=" mailto:mcr@solidum.com ">mcr@solidum.com</A>.
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: noconv
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface
iQCVAwUBNiTh+25vCG0TOZrRAQGhSgP9F65+dK6GmpxT0oJCOJFMutMHQuEl5tOm
z3f7TgbdtOzjLM37pX3xR7l2hXIdJy86dNSpbLr3K5GTMoMmt9GICHuulQjk6XwG
WosDGWnGhoe4DvlqQbv8Q4GB1TVVPGn87DJKqUr6jREzWReEKZCn3rm4qIz0cAbC
4eoA63HP4Y4=
=6Dyv
-----END PGP SIGNATURE-----
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
reply other threads:[~1998-10-15 0:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=199810141740.NAA03024@venus.solidum.com \
--to=mcr@solidum.com \
--cc=feliks@venus.solidum.com \
--cc=gnu-win32@cygnus.com \
--cc=thai@venus.solidum.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).