zsh-workers
 help / color / mirror / code / Atom feed
From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "ZSH workers mailing list" <zsh-workers@sunsite.auc.dk>
Subject: RE: Dynamic loading on Cygwin - status
Date: Fri, 28 Jul 2000 20:17:40 +0400	[thread overview]
Message-ID: <000201bff8af$59daf3f0$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <000101bff8a3$60aad7b0$21c9ca95@mow.siemens.ru>

>
> - for dlsym() to find a symbol, it has to explcitly exported. It means, that
> module's setup() etc functions are not found. They has to be defined with
> __attribute__((__dllexport__)). All exported symbols (that have mod_export)
> currently get this automatically.
>

dllwrap --export-all-symbols

Do you understand now, why Win32 programs have such a size? :-)

(This is quick fix. As we actually need just four functions in addition to
mod_export'ed, it is better to define additional token that is defined on
Cygwin to __attr...)

> - external function or variable imported from another module is not
> considered
> a constant on Cygwin (actually, on Windows). Hence, any static initializer
> fails, e.g

That is really bad. Alternatives are

- compile such module into main DLL. We may somehow automate it by putting
hint into .mdd file
- pretend itself run-time linker and resolve address itself.
- rewrite zsh in C++ ...


Now I *really* have working Zsh will dynamic loading. Unfortunately,
completion is not really useable without parameters module ... just tried

zmodload zsh/mapfile
vared 'mapfile[init.syms]'

it works!

-andrej


  reply	other threads:[~2000-07-28 16:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-28 14:51 Andrej Borsenkow
2000-07-28 16:17 ` Andrej Borsenkow [this message]
2000-07-31 13:58   ` Peter Stephenson
2000-07-31 14:08     ` Andrej Borsenkow

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='000201bff8af$59daf3f0$21c9ca95@mow.siemens.ru' \
    --to=andrej.borsenkow@mow.siemens.ru \
    --cc=zsh-workers@sunsite.auc.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).