From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Standalone Installation Question
Date: Sun, 20 Oct 2013 10:58:55 +0200 [thread overview]
Message-ID: <CAG5iGsBzBAWqYtJqooN8qTP6BEchFAMQUCk8tFXfBTTPfPzPUA@mail.gmail.com> (raw)
In-Reply-To: <20131020165259.1564@binki>
[-- Attachment #1.1: Type: text/plain, Size: 1856 bytes --]
On Sun, Oct 20, 2013 at 9:52 AM, <hwitloc@gmail.com> wrote:
>
>
> I downloaded and ran:
>
> $ sh ./$SETUPFILE --modules=all --engine=luatex --context=current
>
> #
> # The documentation on web page [
> http://wiki.contextgarden.net/ConTeXt_Standalone#General_Information ]
> statess that:
>
> " An intialization script called setuptex is provided in
> installation-dir/tex/.
> " If you run context from a terminal, source setuptex like so:
> " source /installation-dir/tex/setuptex "
>
> BUT, first-setup.sh did not produce and populate any ./tex directory and
> there is no
> setuptex command file.
>
> What can I do to proceed from this point. Currently the /installation
> directory contains:
>
> Reference: first-setup.sh produces the following files and directory
> structure:
>
> $ ls -l
> drwxrwxrwx+ 1 djtm None 0 Oct 20 16:09 .
> drwxr-xr-x 1 djh Users 0 Oct 20 14:06 ..
> drwxr-xr-x+ 1 djh None 0 Aug 7 16:40 bin
> -rwxr-xr-- 1 djh None 3654 Jun 20 22:27 first-setup.sh
>
>
> $ $ ls -l bin
> -rw-r--r-- 1 djh None 999424 Nov 23 2012 cygiconv-2.dll
> -rw-r--r-- 1 djh None 1873396 Nov 23 2012 cygwin1.dll
> -rw-r--r-- 1 djh None 72192 Aug 14 09:29 kpathsea620.dll
> -rw-r--r-- 1 djh None 338944 Aug 14 10:32 lua52.dll
> -rw-r--r-- 1 djh None 6889472 Sep 28 07:03 luatex.dll
> -rw-r--r-- 1 djh None 7680 Apr 16 2013 mtxrun.dll
> -rwxr-xr-x 1 djh None 4608 Apr 16 2013 mtxrun.exe
> -rw-r--r-- 1 djh None 497742 Oct 15 20:54 mtxrun.lua
> -rw-r--r-- 1 djh None 25352 Oct 8 06:31 mtx-update.lua
> -rwxr-xr-x 1 djh None 346112 Nov 23 2012 rsync.exe
> -rwxr-xr-x 1 djh None 1536 Jun 24 22:41 texlua.exe
>
> -------- END
>
hm first-setup.sh is for Linux, but you have a set of Windows files...
so which platform do you need ?
--
luigi
[-- Attachment #1.2: Type: text/html, Size: 2540 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2013-10-20 8:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-20 7:52 hwitloc
2013-10-20 8:58 ` luigi scarso [this message]
2013-10-20 9:23 ` d.henman
2013-10-20 9:46 ` luigi scarso
2013-10-20 13:54 ` hwitloc
2013-10-20 14:05 ` luigi scarso
2013-10-20 16:06 ` hwitloc
2013-10-22 10:04 ` Mojca Miklavec
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=CAG5iGsBzBAWqYtJqooN8qTP6BEchFAMQUCk8tFXfBTTPfPzPUA@mail.gmail.com \
--to=luigi.scarso@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).