Zsh Mailing List Archive
Messages sorted by:
Re: Building a new ZSH module outside the ZSH source tree
- X-seq: zsh-workers 41149
- From: tetsujin@xxxxxxxxxxxxx
- To: zsh-workers@xxxxxxx
- Subject: Re: Building a new ZSH module outside the ZSH source tree
- Date: Wed, 24 May 2017 18:41:02 -0400
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed; d=scope-eye.net; h= message-id:from:to:in-reply-to:subject:date:content-type :mime-version; s=scope-eye.net; bh=TSBOQ50anPRCAZvP8ZxwOrzxEzw=; b= UFoU4J6UU4bwG1v/UPENboiGWa+sa5V5fJ6DxRdCy4AWbQC3eRifrAikkfxMBzrF 5W0pd2ZrIt6TV4IFU6owut99n0Dpvx5rA//dt0W9BQbUF0jl2f/Q6JI8RAF8J4xb PzqErIy2rRRTxq4wN7Y1qxjZ2AKj2oQx5/oS6Tofd48=
- In-reply-to: <170524141902.ZM15541@torch.brasslantern.com>
- List-help: <mailto:email@example.com>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:firstname.lastname@example.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
>On May 24, 2:57pm, tetsujin@xxxxxxxxxxxxx wrote:
>} I'm not really clear on the process for building a module
>} without tying it into the zsh build system.
>I haven't actually tried the following yet.
> --- Forwarded mail from Sebastian Gniazdowski
>1/ Turned out that it's easy to build Zsh modules away from complete
>source. Here is a minimum build setup:
Thanks! Unfortunately it seems this project gets around the issue by
duplicating the zsh source tree and build environment, and planting
the zdharma/zplugin project within it.
It gets the job done, but it's not really ideal. I guess the main
thing (perhaps) is the *.mdh file that gets generated - what it does,
and how I can generate it myself.
"What it does", I guess, is set a bunch of defines to change the
module load/unload functions' names to a form specific to the package
(#define boot_ boot_zdharmaQszplugin for instance) and set some
defines prior to including shell headers...
The way to generate it, I guess, is to run zsh/Src/mkmakemod.sh, which
produces the Makefile for the module, which in turn generates the
module headers and other files.
Perhaps the best answer is to call into the script from my module's
build system, and then use the Makefile it generates. Perhaps that
could even work without having to place my module in a subdirectory of
the shell's build tree? (Not sure about that one.)
Messages sorted by: