zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Adding (compiling) a module to already build Zsh
Date: Wed, 14 Sep 2016 09:19:32 -0700	[thread overview]
Message-ID: <160914091932.ZM29637@torch.brasslantern.com> (raw)
In-Reply-To: <45670.1473843287@hydra.kiddle.eu>

On Sep 14, 10:54am, Oliver Kiddle wrote:
}
} Many of the prototypes are autogenerated with makepro.awk and that
} mechanism ties in to aspects of the module mechanism. So, for example, an
} obvious function to include in the module interface might be addhookdefs
} but the prototype is in module.epro. This may not be a problem as such
} but it'd need someone who understands what's going on in that area.

This.  It's difficult enough right now to add a module directly to the
full zsh tree, much less tease apart all the bits that would need to
be teased in order to build with only a few pre-existing headers.

Packages like libapreq (mod_perl) and the old X11 had similar problems
back in the day.  (I haven't built loadable modules against any of
their successors in many years, so I don't know the current state.)
The decisions we made with .epro files and awk scripts were all good
ones at the time.  If we could find an expert on the current state of
dynamic loading on a variety of platforms, it would be very helpful.


  reply	other threads:[~2016-09-14 16:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-12  6:12 Sebastian Gniazdowski
2016-09-12 17:38 ` Bart Schaefer
2016-09-14  7:16   ` Sebastian Gniazdowski
2016-09-14  8:54     ` Oliver Kiddle
2016-09-14 16:19       ` Bart Schaefer [this message]
2016-09-14 19:03       ` Mikael Magnusson
2016-09-15 12:22         ` Sebastian Gniazdowski
2016-09-14 15:09     ` Lawrence Velázquez

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=160914091932.ZM29637@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@zsh.org \
    /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).