Go to file
Daniel Silverstone 29ce303eb0 Framebuffer: Add symlink to build messages resource
Since framebuffer lacks the language directories in its resources
currently, we need a symbolic link to the en/Messages built in
the top level resources directory in order that nsfb can run
without the Messages file having been installed previously.

Signed-off-by: Daniel Silverstone <dsilvers@digital-scurf.org>
2019-02-15 21:08:35 +00:00
content Box construction: Don't handle IMAGE specially. 2018-12-13 12:31:38 +00:00
desktop Treeview: Consider search bar for redraw area calculation. 2019-01-19 15:12:03 +00:00
docs fix helper script apt packaging to work with buster 2018-11-06 21:55:20 +00:00
frontends Framebuffer: Add symlink to build messages resource 2019-02-15 21:08:35 +00:00
include/netsurf API: Don't expose urldb_{g|s}et_auth_details to frontends. 2018-08-15 07:29:58 +01:00
resources Message: Fix french translation. 2018-11-22 09:39:40 +00:00
test Test: Fix simultanious-fetches.yaml to not look like a YAML alias. 2018-11-04 14:46:46 +00:00
utils ensure filename numeric is not truncated and hence cause output buffer overflow 2018-11-06 21:59:50 +00:00
.clang-format add a clang format that roughly conforms to the netsurf style 2017-09-24 18:19:58 +01:00
.gitattributes add attributes file to stop .gitignore being exported 2013-04-19 21:27:45 +01:00
.gitignore ignore generated Messages files 2018-08-21 13:45:18 +01:00
COPYING Clarify licensing arrangements 2007-08-09 15:32:39 +00:00
Makefile Improve framebuffer install rule 2019-02-15 17:53:31 +00:00
Makefile.config.example Typo fixes 2018-07-28 14:24:31 +01:00
Makefile.defaults Support ASAN and UBSAN in Makefiles 2018-07-28 11:17:07 +01:00
README Fix to point at current build documentaion. 2014-07-22 15:36:36 +01:00

--------------------------------------------------------------------------------
  NetSurf README
--------------------------------------------------------------------------------

  This document should help point you at various useful bits of information.


  Building NetSurf
==================
  
  Read the QUICK-START document in the Docs/ directory for instructions.


  Creating a new port
=====================

  Look at the existing front ends for example implementations.  The framebuffer
  front end is simplest and most self-contained.  Also, you can contact the
  developers for help:

      http://www.netsurf-browser.org/contact/

  Check out the developer documentation sources listed below too.


  Further documentation
=======================

  The Developer section of the web site has loads of info to get you started:

      http://www.netsurf-browser.org/developers/

  General documentation on how NetSurf's code works can be found on the
  development wiki:

      http://wiki.netsurf-browser.org/Documentation/

  The code style guide is here:

      http://www.netsurf-browser.org/developers/StyleGuide.pdf