Skip to content

Updated README #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 24, 2022
Merged

Updated README #9

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions README.markdown
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ can also use github for that, or download parts of the history later.
### Requirements ###

- A recent version of Haiku (beta2 is too old, it lacks at least madvise() and support for compositing draw operations)
- The GCC8 development tools
- The GCC11 development tools
- The dependencies as listed below
- At least about 2G of RAM
- Preferably a fast computer!
Expand Down Expand Up @@ -61,6 +61,9 @@ This will build a release version of WebKit libraries on a quad core cpu.

On a successful build, executables and libraries are generated in the WebKitBuild/Release directory.

##### NOTE:
If you are getting "out of memory" error despite having sufficient memory, disable ASLR:
$ export DISABLE_ASLR=1

### Advanced Build, other targets ###

Expand Down Expand Up @@ -95,7 +98,7 @@ It is a good idea to set the NUMBER\_OF\_PROCESSORS environment variable as well
the local CPUs will be counted, leading to a sub-optimal distcc distribution.

distcc will look for a compiler named gcc-x86 and g++-x86. You'll need to adjust
the path on the slaves to get that pointing to the gcc8 version (the gcc8 compiler
the path on the slaves to get that pointing to the gcc11 version (the gcc11 compiler
is already visible under this name on the local machine and haiku slaves).
CMake usually tries to resolve the compiler to an absolute path on the first
time it is called, but this doesn't work when the compiler is called through
Expand Down