From: Eric McDonald <mcdonald@phy.cmich.edu>
To: "Brandon J. Van Every" <vanevery@indiegamedesign.com>
Cc: xconq <xconq7@sources.redhat.com>
Subject: RE: Canonical Windows build environment?
Date: Mon, 03 Nov 2003 15:02:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0311030858550.2866-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <OOEALCJCKEBJBIJHCNJDIECLGLAB.vanevery@indiegamedesign.com>
Hello Brandon,
On Mon, 3 Nov 2003, Brandon J. Van Every wrote:
> Ok, as per INSTALL-win instructions, I've tried the following with
> Cygwin:
>
> ./configure --x-includes=/usr/src/tcltk-20030901-1/tk/xlib/X11 --with-tc
> lconfig=/lib --with-tkconfig=/lib
Could you send the error output to the list? I would like to look
at it, and if Juergen is around, he might also have something to
say.... The problem with the INSTALL-win document is that it is
an amalgam of his original doc (which dated back roughly 3 years
ago and refered to much older packages) and updated information I
put in. I took the liberty of updating some of his package
references to newer ones, but did not necessarily verify that said
packages still behaved in the way the old ones did. I did not hear
Juergen complain, so I let things be, thinking that I had made
reasonable assumptions. Have you tried building with the
ActiveState Tcl/Tk? I have verified that.
It was my intent to verify things Juergen's way someday, and to do
a purely MinGW32 build. I didn't consider them top priorities
though, since I think the vast majority of our Windows users are
interested in prepackaged binaries rather than building Xconq
themselves.
> get the same choking, looking for Xlib.h. Is that expected? If
Not particularly.
> estimate of when the major overhaul of the config and Makefiles will be
> completed?
I mentioned several weeks ago that the "major surgery" has been
taken care of. Among other things, this means that the Windows and
Unix builds of Xconq have been unified. It doesn't have much to
do with the Tcl/Tk build per se.
Regards,
Eric
next prev parent reply other threads:[~2003-11-03 14:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-03 1:38 Brandon J. Van Every
2003-11-03 2:00 ` Eric McDonald
2003-11-03 3:02 ` anonymous CVS missing Windows stuff? Brandon J. Van Every
2003-11-03 3:09 ` Brandon J. Van Every
2003-11-03 3:15 ` Hans Ronne
2003-11-03 3:36 ` Eric McDonald
2003-11-03 3:26 ` Eric McDonald
2003-11-03 2:43 ` Canonical Windows build environment? Hans Ronne
2003-11-03 3:52 ` MSVC " Brandon J. Van Every
2003-11-03 4:05 ` Eric McDonald
2003-11-03 5:22 ` Hans Ronne
2003-11-03 16:40 ` Juergen Ruehle
2003-11-03 11:20 ` Canonical Windows " Brandon J. Van Every
2003-11-03 15:02 ` Eric McDonald [this message]
2003-11-03 15:21 ` Juergen Ruehle
2003-11-03 15:52 ` Brandon J. Van Every
2003-11-03 16:57 ` Eric McDonald
2003-11-03 22:18 ` Brandon J. Van Every
2003-11-03 22:48 ` Eric McDonald
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=Pine.LNX.4.44.0311030858550.2866-100000@leon.phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=vanevery@indiegamedesign.com \
--cc=xconq7@sources.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).