From: jamos@oboj.net
To: 9front@9front.org
Subject: Re: [9front] Libpng and Zlib updates on the ports tree
Date: Fri, 14 Feb 2020 08:37:31 +0200 [thread overview]
Message-ID: <8736ee177e816129021806f89c7b62cd@oboj.net> (raw)
In-Reply-To: <4CC3651323A34E493B36D02455B1C664@hera.eonet.ne.jp>
Kenji,
I am glad you worked it out. I was preparing a lengthy reply detailing
what you already found out now. I am waiting for libpng to compile
cleanly in ports before I change the mkfile to include support. JPEG
already works though. As an alternative to changing PNG_ZLIB_VERNUM you
can apply Uramekus patch. Do your nsfb still crash viewing BBC News
(linked from the welcome page)? It has started to work for me.
> 1) use /sys/ports/ape-libs/ libjpeg libpng zlib, the last can replace
> /sys/src/ape/lib/z
> 2) the zlib's version is 1.2.7, then one line change of
> ape-libs/libpng/work/libpng-1.6.17/pnglibcon.h
> #define PNG_ZLIB_VERNUM 0x1280
> to:
> #define PNG_ZLIB_VERNUM 0x1270
> compile above.
>
> 3) nsport/netsurf/mkfile, uncomment
> # content/handlers/image/jpeg.$O \
> # content/handlers/image/png.$O \
>
> CC=pcc -DWITH_BMP -DWITH_GIF -DWITH_BMP -DWITH_JPEG -DWITH_PNG
One might ask why to link against libjpeg and libpng when image viewing
functions are alredy available natively in 9front. This is a valid
question, but as it stands, netsurf as a whole is compiled using APE,
and its viewers are made to use libjpeg and libpng which are also APE
libs. At least we have avoided including ‘libgnu’ (an extension of APE,
also available in ports, using a lot of messy GNU code) and are only
using standard APE and some support libraries that also use standard APE
to compile.
Jonas
next prev parent reply other threads:[~2020-02-14 6:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 1:33 kokamoto
2020-02-14 6:37 ` jamos [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-02-14 7:16 kokamoto
2020-02-14 0:29 kokamoto
2020-02-12 23:19 kokamoto
2020-02-12 20:51 Lucas Francesco
2020-02-12 21:01 ` [9front] " ori
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=8736ee177e816129021806f89c7b62cd@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).