update quick build instructions to include notes on env script
This commit is contained in:
parent
23d9f7040d
commit
c543e3c61c
|
@ -1,6 +1,8 @@
|
|||
Development
|
||||
===========
|
||||
|
||||
[TOC]
|
||||
|
||||
# Working with the team
|
||||
|
||||
Generally it is sensible to check with the other developers if you are
|
||||
|
|
|
@ -1,8 +1,13 @@
|
|||
NetSurf web browser
|
||||
===================
|
||||
|
||||
![CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/1037/badge)[*](https://bestpractices.coreinfrastructure.org/projects/1037)
|
||||
![CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/1037/badge)
|
||||
|
||||
# [Project](docs/project.md)
|
||||
# [User Interface](docs/user-interface.md)
|
||||
# [Development](docs/development.md)
|
||||
[CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/1037)
|
||||
|
||||
|
||||
[Project](docs/project.md)
|
||||
|
||||
[User Interface](docs/user-interface.md)
|
||||
|
||||
[Development](docs/development.md)
|
|
@ -1,10 +1,21 @@
|
|||
Quick Build Steps for NetSurf
|
||||
=============================
|
||||
|
||||
Last Updated: 15th December 2017
|
||||
Last Updated: 21st January 2020
|
||||
|
||||
This document provides steps for building NetSurf.
|
||||
|
||||
These instructions use a shell script to perform several operations.
|
||||
This script has only been tested with the bash and zsh bourne style
|
||||
shell interpreters. The latest version of this script should be
|
||||
retrieved from the official NetSurf source repository.
|
||||
|
||||
This shell script is used by the NetSurf Developers but you should
|
||||
satisfy yourself that the script is not malicious. It should be noted
|
||||
that the building the browser will also be executing shell code and
|
||||
requires a similar level of trust.
|
||||
|
||||
|
||||
Native build
|
||||
============
|
||||
|
||||
|
|
|
@ -1,6 +1,8 @@
|
|||
User Interface
|
||||
==============
|
||||
|
||||
[TOC]
|
||||
|
||||
Netsurf is divided into a series of frontends which provide a user
|
||||
interface around common core functionality. Each frontend is a
|
||||
distinct implementation for a specific GUI toolkit.
|
||||
|
|
Loading…
Reference in New Issue