ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Henning Hraban Ramm <texml@fiee.net>
Subject: Re: zint barcode module on LMTX/MacOS
Date: Sun, 5 Sep 2021 18:30:20 +0200	[thread overview]
Message-ID: <66433472-1730-4A6F-87ED-BA3B19749DB3@fiee.net> (raw)
In-Reply-To: <CE22LC1BNJB1.39SN8WB6FOLUW@phobos>

Hi Michal, thank you!

> Am 05.09.2021 um 17:51 schrieb Michal Vlasák <lahcim8@gmail.com>:
> 
> On Sun Sep 5, 2021 at 4:15 PM CEST, Henning Hraban Ramm via ntg-context wrote:
>> Hi again,
>> 
>> the LMTX zint module uses libzint, while MkIV calls the zint binary.
>> The latter works for me, the first not.
>> 
>> On MacOS, the library is "/opt/local/lib/libzint.dylib"*.
>> I changed that in the source and the file appears to be found.
>> Could you add that, Hans?
> 
> From libraries-mkiv:
> 
>    It is best to keep libraries in a place where you can keep an eye on
>    them being updated, like
> 
>         c:/data/tex-context/tex/texmf-win64/bin/lib/luametatex/foo/libfoo.dll

Oh, yes, I should still know that from mujs. Works with a symlink.
I.e. no need to change that in the module.

>> But then still zintlib.execute returns nothing.
> 
> I can confirm this as well.
> 
>> I wonder if this works on Windows?
>> The API docs don’t mention an "execute" function.
>> https://www.zint.org.uk/manual/chapter/5
> 
> "execute" should be a function defined in LuaMetaTeX, that internally
> calls zint functions.

Hm, ok, but where are the zint API calls defined?


Hraban
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2021-09-05 16:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-05 14:15 Henning Hraban Ramm via ntg-context
2021-09-05 15:51 ` Michal Vlasák via ntg-context
2021-09-05 16:30   ` Henning Hraban Ramm via ntg-context [this message]
2021-09-05 17:00     ` Michal Vlasák via ntg-context
2021-09-05 17:37   ` Hans Hagen via ntg-context
2021-09-05 17:53     ` Michal Vlasák via ntg-context
2021-09-05 19:01       ` Henning Hraban Ramm via ntg-context
2021-09-05 23:13       ` Hans Hagen via ntg-context
2021-09-06  8:34         ` Henning Hraban Ramm via ntg-context
2021-09-06 11:08           ` Hans Hagen via ntg-context
2021-09-07 19:03             ` Henning Hraban Ramm via ntg-context
2021-09-08  7:05               ` Axel Kielhorn via ntg-context
     [not found]               ` <08952543-f2cb-8c11-d8ab-436cddbc3189@klankschap.nl>
2021-09-08 17:08                 ` Henning Hraban Ramm via ntg-context
2021-09-08 18:49                   ` Floris van Manen via ntg-context

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=66433472-1730-4A6F-87ED-BA3B19749DB3@fiee.net \
    --to=ntg-context@ntg.nl \
    --cc=texml@fiee.net \
    /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.
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).