ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: damien thiriet via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: damien@thiriet.web4me.fr
Subject: [NTG-context] OBSD 7.3 binary locally compiled… what next?
Date: Thu, 04 May 2023 12:11:38 +0200	[thread overview]
Message-ID: <2816df5310e961df62e4b876d974a7c7@thiriet.web4me.fr> (raw)

Hi,


I upgraded today my OBSD to 7.3 and… realized too late that texlive 
binaries were on the compile farm, but not the lmtx ones. That was the 
opportunity to learn self-install, though.
I compiled the binary, but I am stuck with the next step

What I did:

- rm -rf /usr/local/context/* (now I suspect I should have first updated 
my 7.2 installation and then, after upgrading to 7.3, compiled the 
binaries…)
- download  https://www.pragma-ade.nl/context/latest/cont-tmf.zip
- unpacked it into /usr/local/context (unzip cont-tmf.zip -d 
/usr/local/context/)
- cd /usr/local/context/source/luametatex
- ./build.sh --native

Compilation succeeded, looks like the binary lies in
/usr/local/context/source/luametatex/build/native/luametatex

What's the next step?

There was this message:

==============
tex trees

resources like public fonts  : tex/texmf/....
the context macro package    : tex/texmf-context/....
the luametatex binary        : tex/texmf-native/bin/...
optional third party modules : tex/texmf-context/....
fonts installed by the user  : tex/texmf-fonts/fonts/data/....
styles made by the user      : tex/texmf-projects/tex/context/user/....

binaries:

tex/texmf-<your platform>/bin/luametatex     : the compiled binary (some 
2-3MB)
tex/texmf-<your platform>/bin/mtxrun         : copy of or link to 
luametatex
tex/texmf-<your platform>/bin/context        : copy of or link to 
luametatex
tex/texmf-<your platform>/bin/mtxrun.lua     : copy of 
tex/texmf-context/scripts/context/lua/mtxrun.lua
tex/texmf-<your platform>/bin/context.lua    : copy of 
tex/texmf-context/scripts/context/lua/context.lua

commands:

mtxrun --generate                 : create file database
mtxrun --script fonts --reload    : create font database
mtxrun --autogenerate context ... : run tex file (e.g. from editor)
https://www.pragma-ade.nl/context/latest/cont-tmf.zip

The tex/texmf/ folder does not exist yet.

Does this mean I have to create that part of the tree by hand (which 
means should I have unpacked the zip at /usr/local/context/tex/texmf 
rather than /usr/local/context)?I’d bet copying anything(copying mtxrun 
from
/usr/local/context/scripts/context/stubs/unix/mtxrun ?

Should I run install.sh – which I not did, assuming maybe wrongly that 
it would fail, and if so, which options?

Thank you for your time,

Damien

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

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

             reply	other threads:[~2023-05-04 10:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-04 10:11 damien thiriet via ntg-context [this message]
2023-05-04 10:56 ` Hans Hagen via ntg-context
2023-05-08 21:52 damien thiriet 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=2816df5310e961df62e4b876d974a7c7@thiriet.web4me.fr \
    --to=ntg-context@ntg.nl \
    --cc=damien@thiriet.web4me.fr \
    /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).