zsh-workers
 help / color / mirror / code / Atom feed
From: Borsenkow Andrej <Andrej.Borsenkow@mow.siemens.ru>
To: Zsh hackers list <zsh-workers@sunsite.dk>
Subject: Re: PATCH: zsh/pcre module building
Date: 22 Mar 2002 17:24:08 +0300	[thread overview]
Message-ID: <1016807054.3021.12.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44.0203181722570.19248-100000@ns1.sodaware.com>

В Втр, 19.03.2002, в 04:29, Bart Schaefer написал:
> On Fri, 15 Mar 2002, Clint Adams wrote:
> 
> > Here's a different method to avoid linking the zsh binary against
> > libpcre.
> 
> So if I comprehend what's going on here correctly, this links the zsh/pcre
> module against libpcre, but doesn't link the zsh binary against it?
> 
> This seems like a good thing.  Could it perhaps also be applied to the
> termcap and terminfo modules?
> 

I have been thinking about it before, just some comments

- I hoped to create implementation that would share configure cache and
make is possible to list help from every module's configure script using
top-level configure --help and pass parameters to every module's
configure script using top-level configure. Using stock autoconf it is
possible only with fixed number of sub-scripts; but may be it is enough
(we may distribute zsh in this way and for developers additional script
that would create needed definitions for modules).

- linking shared object with dynamic library is not portable. May be it
works on every modern system nowadays, I do not know. 

-andrej


  reply	other threads:[~2002-03-22 14:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-15 18:07 Clint Adams
2002-03-19  1:29 ` Bart Schaefer
2002-03-22 14:24   ` Borsenkow Andrej [this message]
2002-03-23 19:57     ` Bart Schaefer
2002-03-23 23:47       ` Clint Adams
2002-07-04 17:07     ` Clint Adams
2002-07-05 10:39       ` Borsenkow Andrej
2002-03-21 19:14 ` Borsenkow Andrej
2002-03-21 20:15   ` Peter Stephenson
2002-03-21 20:37     ` Bart Schaefer
2003-06-23  4:35 Fr�d�ric L. W. Meunier

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=1016807054.3021.12.camel@localhost.localdomain \
    --to=andrej.borsenkow@mow.siemens.ru \
    --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).