From: jamos@oboj.net
To: 9front@9front.org
Subject: Re: [9front] adding javascript enable to netsurf
Date: Sun, 15 Mar 2020 15:50:09 +0200 [thread overview]
Message-ID: <2866c85ea803dc041fe009a820be38d4@oboj.net> (raw)
In-Reply-To: <41AE2FAE-9904-401B-A822-7E41389E1668@quintile.net>
That might be another way than we are taking now. The Amiga frontend can
either be compiled natively or cross compiled from Linux (se building-*
files here http://source.netsurf-browser.org/netsurf.git/tree/docs).
Anyhow, we already copy the autogenerated output from perl, flex, bison
and python, right now. Ori’s suggestion to move the autogenerated files
into the ‘nsport’ repository will probably make it easier to merge e.g.
libcss with the upstream libcss, as our ‘patching’ will reside in nsport
(which is not cloned from any upstream repo).
It is a pity that the lexer and parser generator require GNU tools
(flex/bison), when Plan 9 already contains the original tools
(lex/yacc). If someone is good in lex/flex and yacc/bison, it would be
interesting to see if these files could be made to work in both
environments. But maybe it is like with bash vs sh in Go, that the win
is to keep with one well defined interface. An other alternative would
be to write a translator, it doesn’t necessarily have to be complete.
Jonas
On 2020-03-15 13:06, Steve Simon wrote:
> Hi,
>
> just a thought, but what is the hope of cross compiling on linux with
> plan9 as a target?
>
> it would need to include a /dev/draw backend and be statically linked,
> but perhaps it might be a simpler path to a working browser.
>
> -Steve
>
> On 15 Mar 2020, at 9:42 am, kokamoto@hera.eonet.ne.jp wrote:
>
> Yeah. for now, best option is to generate on Unix,
> I followed you, and got compiled netsurf-3.9 on my Ubuntu18.04.
> Now I have the vision of what is the goal of version 3.9.
>
> Kenji
next prev parent reply other threads:[~2020-03-15 13:50 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-15 9:42 kokamoto
2020-03-15 11:06 ` Steve Simon
2020-03-15 11:38 ` Jens Staal
2020-03-15 13:50 ` jamos [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-04-14 5:04 kokamoto
2020-04-14 21:53 ` Kyle Nusbaum
2020-04-15 20:05 ` jamos
2020-04-15 20:24 ` ori
2020-04-18 1:09 ` Kyle Nusbaum
2020-04-18 1:19 ` ori
2020-04-18 17:11 ` Eli Cohen
2020-04-18 17:15 ` telephil9
2020-04-18 17:17 ` ori
2020-04-13 23:46 kokamoto
2020-04-07 4:25 kokamoto
2020-04-06 5:48 kokamoto
2020-04-13 12:44 ` jamos
2020-04-05 4:52 kokamoto
2020-04-05 4:41 kokamoto
2020-03-22 23:47 kokamoto
2020-03-22 2:19 kokamoto
2020-03-21 3:24 kokamoto
2020-03-22 20:27 ` jamos
2020-03-22 20:54 ` ori
2020-03-22 20:54 ` ori
2020-03-20 5:49 kokamoto
2020-03-20 16:10 ` Kyle Nusbaum
2020-03-20 16:15 ` ori
2020-03-20 17:12 ` telephil9
2020-03-20 17:40 ` Jens Staal
2020-03-20 18:54 ` jamos
2020-03-21 5:00 ` Jens Staal
2020-03-21 12:24 ` Ethan Gardener
2020-03-20 22:07 ` Kyle Nusbaum
2020-03-17 11:16 kokamoto
2020-03-17 17:42 ` jamos
2020-03-14 1:49 kokamoto
2020-03-14 2:09 ` ori
2020-03-14 1:19 kokamoto
2020-03-14 1:34 ` ori
2020-03-13 4:33 kokamoto
2020-03-13 4:58 ` ori
2020-03-12 5:28 kokamoto
2020-03-12 2:20 kokamoto
2020-03-12 2:43 ` ori
2020-03-11 23:59 kokamoto
2020-03-11 10:27 kokamoto
2020-03-11 6:36 kokamoto
2020-03-11 9:29 ` [9front] " jamos
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=2866c85ea803dc041fe009a820be38d4@oboj.net \
--to=jamos@oboj.net \
--cc=9front@9front.org \
/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).