zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: Where to add extra libraries for modules
Date: Mon, 23 Jul 2001 16:31:43 +0000	[thread overview]
Message-ID: <1010723163143.ZM13997@candle.brasslantern.com> (raw)
In-Reply-To: <m2y9phybno.fsf@freebie.phydeaux.org>

On Jul 21,  9:50pm, Fletch wrote:
} 
}         I've all but got my perl-in-zsh module working with 4.0.2
} again, but I've got an issue with where I should be adding in the
} commands to link against the perl libraries.
} 
}         Would it make sense (possibly) to add an `extralibs' paramter
} in the .mdd and then have mkmakemod.sh include that in the rule for
} module.$(DL_EXT)?

We had a short discussion about this back when termcap/terminfo became
modules.  The above would work for Perl, I think, but it won't work for
new modules in general -- the difficult bit comes when some sort of
configure-time testing is needed in order to detect the availability or
local install location of such extra libraries.  At this point there's
nowhere other than zsh's configure script where such tests can be added.

Another question is whether `extralibs' is enough.  Do we need separate
entries for dynamic v. static?  (And is `extralibs' the best name?)

One possibility would be to have `extralibs' or whatever, be an eval'd
value like `link' is.  It'd be evaluated at configure time and then the
result would be copied into config.modules.  We'd have to fix parsing
of that file to permit multiple libraries -- currently in every name=val
pair except the last on the line (`functions'), val has to be exactly
one word.

Then there's the additional question, which someone raised earlier, of
being able to compile zsh modules independently of compiling the shell
itself.  At present I think this would require installing all the .epro
files in an include directory (/usr/local/include/zsh/$(VERSION)/ ?) and
also makepro.awk, mkmakemod.sh, and the generated Makemod (or a subset
of it) somewhere.  What other files am I forgetting?

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   


  parent reply	other threads:[~2001-07-23 16:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-22  1:50 Fletch
2001-07-22  5:08 ` Andrej Borsenkow
2001-07-22 15:43   ` Fletch
2001-07-23  4:32     ` Andrej Borsenkow
2001-07-23 16:31 ` Bart Schaefer [this message]
2001-07-30 15:25   ` Clint Adams

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=1010723163143.ZM13997@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=zsh-workers@sunsite.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).