security/hakurei.app
security/hakurei.app
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 4 Wiki Activity

restructure source page

Browse Source
This commit is contained in:
Daniel Micay 2020-12-25 22:51:32 -05:00
parent c371cef8c5
commit b578d659b7
1 changed files with 32 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

48
static/source.html
View File

@ -52,23 +52,39 @@
<a href="/contact#reporting-issues">reporting issues section on the contact page</a> <a href="/contact#reporting-issues">reporting issues section on the contact page</a>
for an comparable overview of where issues should be filed.</p> for an comparable overview of where issues should be filed.</p>
<ul> <nav id="table-of-contents">
<li><a href="https://github.com/GrapheneOS/platform_manifest">Manifest for OS repositories</a></li> <h2><a href="#table-of-contents">Table of contents</a></h2>
<li><a href="https://github.com/GrapheneOS/hardened_malloc">hardened_malloc</a></li>
</ul>
<p>The operating system source tree includes hundreds of repositories. Many of these <ul>
are only used for debugging, testing or development and are not actually part of what <li><a href="#grapheneos">GrapheneOS</a></li>
gets used for building a production release. The manifest repository references all of <li><a href="#standalone-apps">Standalone apps</a></li>
these. Most of these are used unmodified from the Android Open Source Project (AOSP). <li><a href="#services">Services</a></li>
A few dozen of the repositories including most of the core OS are either forked from <li><a href="#utilities">Utilities</a></li>
AOSP or are unique to GrapheneOS. The operating system has a unified build system, but <li><a href="#archive">Archive</a></li>
some components like Chromium are too complex to fit into it so they're included as </ul>
prebuilts instead of porting them to the AOSP build system. This is also done for </nav>
developer convenience and bootstrapping, to avoid needing to build all the native /
cross-compilation toolchains for each host and target platform combination, etc. The <section id="grapheneos">
prebuilts can all be built from source if desired. The build instructions will be <h2><a href="#grapheneos">GrapheneOS</a></h2>
expanded to cover all of this in the future.</p>
<ul>
<li><a href="https://github.com/GrapheneOS/platform_manifest">Manifest for OS repositories</a></li>
<li><a href="https://github.com/GrapheneOS/hardened_malloc">hardened_malloc</a></li>
</ul>
<p>The operating system source tree includes hundreds of repositories. Many of these
are only used for debugging, testing or development and are not actually part of what
gets used for building a production release. The manifest repository references all of
these. Most of these are used unmodified from the Android Open Source Project (AOSP).
A few dozen of the repositories including most of the core OS are either forked from
AOSP or are unique to GrapheneOS. The operating system has a unified build system, but
some components like Chromium are too complex to fit into it so they're included as
prebuilts instead of porting them to the AOSP build system. This is also done for
developer convenience and bootstrapping, to avoid needing to build all the native /
cross-compilation toolchains for each host and target platform combination, etc. The
prebuilts can all be built from source if desired. The build instructions will be
expanded to cover all of this in the future.</p>
</section>
<section id="standalone-apps"> <section id="standalone-apps">
<h2><a href="#standalone-apps">Standalone apps</a></h2> <h2><a href="#standalone-apps">Standalone apps</a></h2>