From: Hans Hagen <j.hagen@xs4all.nl>
To: "Jairo A. del Rio" <jairoadelrio6@gmail.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: About loading C libraries (again)
Date: Thu, 5 Nov 2020 10:08:09 +0100 [thread overview]
Message-ID: <938f07df-b538-8d66-12ce-37bbef008c9b@xs4all.nl> (raw)
In-Reply-To: <CAKyqqaZzV4yCbTo8YUdecdb1daq2C4_s_2aVOTEam8FyL-yTSw@mail.gmail.com>
On 11/5/2020 3:42 AM, Jairo A. del Rio wrote:
> Hi again. I grepped the new release and I see permitloadlib is already
> included in mtxrun. Just out of curiosity, is --permitloadlib called via
> context or should I use it from mtxrun?
> context --permitloadlib file.tex still doesn't have any effect.
It does here (not that i have a lib to test) so maybe check your path:
.../tex-context/tex/texmf-win64/bin/lib/luametatex/foo/libfoo.dll
(put the file there and run mtxrun --generate)
The lua versions should match and there shopuld be the initialer function.
\enabletrackers[*lib*]
gives some info.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2020-11-05 9:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 10:01 Jairo A. del Rio
2020-11-04 11:44 ` Hans Hagen
2020-11-05 2:42 ` Jairo A. del Rio
2020-11-05 9:08 ` Hans Hagen [this message]
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=938f07df-b538-8d66-12ce-37bbef008c9b@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=jairoadelrio6@gmail.com \
--cc=ntg-context@ntg.nl \
/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).