From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: UWIN?
Date: Fri, 14 Jun 2013 09:07:09 +0200 [thread overview]
Message-ID: <CAG5iGsB9_fvdhXKL5er0+njxOHSQFCmU5px+ahTsjYT==XV+QA@mail.gmail.com> (raw)
In-Reply-To: <000f01ce6898$a7e1e4c0$f7a5ae40$@net>
[-- Attachment #1.1: Type: text/plain, Size: 451 bytes --]
On Fri, Jun 14, 2013 at 2:46 AM, Bill Meahan <subscribed_lists@meahan.net>wrote:
> Out of curiosity, has anyone tried porting ConTeXt to the UWIN
> environment?
>
> no, honestly the binaries from A. Kakuto are
ok, and also the mingw version works.
The Lua scripts are almost OS independent and the TeX code is
OS independent (ok I should say almost too)
and very likely a uwin porting is (a bit or much) slower than the native
one
so...
--
luigi
[-- Attachment #1.2: Type: text/html, Size: 922 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-06-14 7:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 0:46 UWIN? Bill Meahan
2013-06-14 7:07 ` luigi scarso [this message]
2013-06-14 7:40 ` UWIN? Hans Hagen
2013-06-14 10:58 ` UWIN? Bill Meahan
2013-06-14 12:21 ` UWIN? Jacob Peck
2013-06-14 19:05 ` UWIN? Mojca Miklavec
2013-06-14 19:13 ` UWIN? Jacob Peck
2013-06-14 20:14 ` UWIN? Mojca Miklavec
2013-06-14 21:51 ` UWIN? Jacob Peck
2013-06-15 15:48 ` UWIN? Bill Meahan
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='CAG5iGsB9_fvdhXKL5er0+njxOHSQFCmU5px+ahTsjYT==XV+QA@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).