re: netsurf-sdl on Windows?

On Tue, 2012-05-08 at 09:44 -0400, LM wrote:

> > Why not use the native Windows frontend?
> >
> > The framebuffer frontend is totally unsuitable for use on systems that
> > have a full-featured window manager.
>
> I was hoping to use the SDL version on a couple of platforms including
> Windows. I suppose I could build each one natively though. If I can
> get it to build, long-term plan was not to use it as a web browser,
> but more of a cross-platform replacement for dialog. Was thinking I
> could possibly replace the part that sends form data to a server with
> the ability to store the information locally to a file. I wouldn't
> even need the web access capabilities, just the capabilities to
> interpret HTML and CSS and render pages. There are cross-platform
> replacements for dialog, but I'd really like to have something that
> can use standard web syntax (HTML, CSS, etc.) for creating interfaces.

I really don't think NetSurf is suited to this scenario at all. There
are many assumptions within NetSurf that there is a server to talk to.
You'd probably be better off looking for a standalone rendering engine,
which NetSurf is not (and is unlikely to be in the short to medium
term).

> When I run make TARGET=windows I see no error messages. I redirected
> standard output and standard error to a file.

The reason I asked for the exact build output is that it saves us both
time and speculation. Please do the following:

1) make TARGET=windows clean
2) make TARGET=windows Q= >buildlog-win 2>&1
3) Send the verbatim buildlog-win to me

> Checking the build-windows-windows directory, I see object files
> (108 of them). There are no libraries or executables built.

The output binary is placed in the top level of the source tree, not in
the build-* directory. For the Windows target, it is called NetSurf.exe

> When I tried running make TARGET=framebuffer, I got several errors
> back. Some of them include:
> image/mng.c:29:20: fatal error: libmng.h: No such file or directory
> [ I thought I had MNG disabled, but appears framebuffer mode still
> wants the library installed. ]

It uses the same configuration file as all the other frontends, so it's
unlikely to explicitly want it. How have you disabled MNG?

> framebuffer/thumbnail.c:66:16: error: 'NSFB_SURFACE_RAM' undeclared
> (first use in this function)
> framebuffer/thumbnail.c:71:41: error: 'NSFB_FMT_XBGR8888' undeclared
> (first use in this function)
> framebuffer/thumbnail.c:73:2: error: incompatible type for argument 1
> of 'nsfb_init'
> framebuffer/thumbnail.c:90:2: error: too many arguments to function
> 'nsfb_plot_copy'

These failures are symptomatic of building against the wrong version of
libnsfb. If you are building from a release tarball, then the correct
libraries are bundled with it. If you are building from an SVN snapshot,
please ensure that you have snapshots of the libraries from the same
revision.

> framebuffer/convert_image.c:22:17: fatal error: png.h: No such file or directory
> [ My png.h is in /usr/local/include. I'm guessing if this was
> switched from <png.h> to "png.h", it'll find it. ]

No, it won't. You need to ensure that /usr/local/include is on the
include path (or, ideally, ensure that pkg-config reports the correct
paths when asked)

> cc.exe: error: build-windows-framebuffer/caret_image.c: No such file
> or directory
> cc.exe: fatal error: no input files
> compilation terminated.
> make: *** [build-windows-framebuffer/build-windows-framebuffer_caret_image.o]
> Error 1

Again, please do the following:

1) make TARGET=framebuffer clean
2) make TARGET=framebuffer Q= >buildlog-fb 2>&1
3) Send the verbatim buildlog-fb to me


John-Mark.