From: Mo DeJong <supermo@bayarea.net>
To: sourcenav@sources.redhat.com
Cc: insight@sources.redhat.com
Subject: Patch for fix libgui compile under VC++
Date: Fri, 22 Feb 2002 03:50:00 -0000 [thread overview]
Message-ID: <20020222024222.394b88a4.supermo@bayarea.net> (raw)
Hi all.
I noticed that the recent import of tkTable 2.7 has broken the
libgui build under VC++. The patch to fix the problem is
attached. This change should have no effect under Unix
systems.
2002-02-22 Mo DeJong <supermo@bayarea.net>
* src/Makefile.am: Add -DBUILD_tkTable define so
that newly imported tkTable sources compile
with VC++.
* src/Makefile.in: Regen.
--- /tmp/Makefile.am Fri Feb 22 02:32:52 2002
+++ src/Makefile.am Fri Feb 22 02:23:27 2002
@@ -49,3 +49,4 @@
-DTBL_COMMAND=\"$(TBL_COMMAND)\"\
--DTBL_RUNTIME=\"tkTable.tcl\" -DTBL_RUNTIME_DIR=\"$(guidir)\"
+-DTBL_RUNTIME=\"tkTable.tcl\" -DTBL_RUNTIME_DIR=\"$(guidir)\"\
+-DBUILD_tkTable
next reply other threads:[~2002-02-22 10:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-22 3:50 Mo DeJong [this message]
2002-02-22 15:53 ` Mo DeJong
2002-02-23 17:41 ` Keith Seitz
2002-02-23 17:44 ` Mo DeJong
2002-02-24 14:23 ` 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=20020222024222.394b88a4.supermo@bayarea.net \
--to=supermo@bayarea.net \
--cc=insight@sources.redhat.com \
--cc=sourcenav@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).