From: Alexandre Petit-Bianco <apbianco@cygnus.com>
To: rhug-rhats@sources.redhat.com
Subject: Jython dependencies...
Date: Wed, 17 Oct 2001 17:39:00 -0000 [thread overview]
Message-ID: <200110180039.RAA06254@fencer.cygnus.com> (raw)
I'm experimenting with a Makefile.am file for jython. I haven't solved
the `make install' issue yet. But I have questions regarding this
section:
# Several libraries define what readline needs (tgetnum for instance
# is defined in libcurses, libncurses and libtermcap.) The one we need
# should be found at configure time. FIXME.
TEST_LDADD_LIBS = -lreadline -lcurses
# There has to be a better way to specify these extra
# libraries. FIXME.
TEST_DEPS = ../jakarta-servletapi/lib-javax-servlet.la \
../jakarta-oro/lib-org-apache-oro.la \
../gnu.readline/lib-org-gnu-readline.la
test_SimpleEmbedded_DEPENDENCIES = $(TEST_DEP)
test_SimpleEmbedded_SOURCES = upstream/src/Demo/embed/SimpleEmbedded.java
test_SimpleEmbedded_LDFLAGS = --main=SimpleEmbedded
test_SimpleEmbedded_LDADD = -L. -l-org-jython $(TEST_DEPS) $(TEST_LDADD_LIBS)
First, I guess I should hack configure.in to check for the curses
libraries (and others) availability and let it replace macros in
TEST_LDADD_LIBS. We need to check for readline too, in order to figure
how we build the gnu.readline. I haven't done that yet.
Second, is this the right way to express libraries dependencies on the
two jython test examples?
./A
next reply other threads:[~2001-10-17 17:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-17 17:39 Alexandre Petit-Bianco [this message]
2001-10-17 18:30 ` Anthony Green
2001-10-17 18:42 ` Alexandre Petit-Bianco
2001-10-17 18:53 ` Tom Tromey
2001-10-17 19:03 ` Alexandre Petit-Bianco
2001-10-17 21:03 ` Anthony Green
2001-10-17 22:04 ` Alexandre Petit-Bianco
2001-10-19 16:30 ` Alexandre Petit-Bianco
2001-10-20 11:14 ` Tom Tromey
2001-10-20 21:57 ` Alexandre Petit-Bianco
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=200110180039.RAA06254@fencer.cygnus.com \
--to=apbianco@cygnus.com \
--cc=rhug-rhats@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).