system/serenity
system/serenity
1
0
Fork 0
mirror of https://github.com/SerenityOS/serenity synced 2024-10-01 21:53:54 +00:00
Code Issues Packages Projects Releases Wiki Activity
60939 commits 2 branches 0 tags 509 MiB
C++ 88%
JavaScript 4.8%
HTML 3.3%
C 1%
CMake 0.8%
Other 2%
Find a file
Sergey Bugaev 0bb37f9c0e AK: Include <features.h> before checking for platform macros 
AK/Platform.h did not include any other header file, but expected
various macros to be defined. While many of the macros checked here are
predefined by the compiler (i.e. GCC's TARGET_OS_CPP_BUILTINS), some
may be defined by the system headers instead. In particular, so is
__GLIBC__ on glibc-based systems.

We have to include some system header for getting __GLIBC__ (or not).
It could be possible to include something relatively small and
innocuous, like <string.h> for example, but that would still clutter
the name space and make other code that would use <string.h>
functionality, but forget to include it, build on accident; we wouldn't
want that. At the end of the day, the header that actually defines
__GLIBC__ (or not) is <features.h>. It's typically included from other
glibc headers, and not by user code directly, which makes it unlikely
to mask other code accidentlly forgetting to include it, since it
wouldn't include it in the first place.

<features.h> is not defined by POSIX and could be missing on other
systems (but it seems to be present at least when using either glibc or
musl), so guard its inclusion with __has_include().

Specifically, this fixes AK/StackInfo.cpp not picking up the glibc code
path in the cross aarch64-gnu (GNU/Hurd on 64-bit ARM) Lagom build.
2024-05-02 07:46:53 -06:00
.devcontainer Meta: Switch to clang-format-18 as the standard formatter 2024-04-24 16:50:01 -04:00
.github CI: Use a local GitHub Action to setup installed packages 2024-05-02 06:22:10 -06:00
AK AK: Include <features.h> before checking for platform macros 2024-05-02 07:46:53 -06:00
Base Browser: Add support for a singleton chrome process 2024-04-30 17:43:14 -06:00
Documentation Meta: Switch to clang-format-18 as the standard formatter 2024-04-24 16:50:01 -04:00
Kernel Kernel/riscv: Use new DeviceTree helpers in PCI initializations 2024-05-02 07:44:13 -06:00
Ladybird Ladybird+LibWebView: Introduce a cache for cookies backed by SQL storage 2024-05-01 07:06:26 +02:00
Meta Meta/run.py: Bring back SERENITY_EXTRA_QEMU_ARGS 2024-05-02 07:44:13 -06:00
Ports Toolchain: Update LLVM to 18.1.3 2024-04-18 13:14:33 -06:00
Tests LibWeb: Implement XMLHttpRequest.responseURL 2024-05-01 12:52:03 +02:00
Toolchain Toolchain/Stubs: Fix small typo in README.md 2024-04-28 07:25:41 -06:00
Userland LibGfx: Explicitly cast literals to size_t in JBIG2Loader 2024-05-02 07:46:53 -06:00
.clang-format Meta: Support using clang-format on Objective-C++ files 2023-08-22 21:36:19 -04:00
.clang-tidy Meta: Disable readability-function-cognitive-complexity in clang-tidy 2024-02-05 08:04:24 -07:00
.editorconfig Meta: Add .editorconfig 2022-09-10 17:32:55 +01:00
.gitattributes Repository: Protect port patches from CRLF/LF normalization 2022-01-12 01:08:38 +01:00
.gitignore Meta: Move .DS_Store rule to the bottom of the .gitignore file 2023-11-14 14:53:37 -05:00
.gn Meta: Automatically generate a compilation database for clangd 2023-11-14 14:29:35 -05:00
.mailmap Everywhere: Update copyrights with my new serenityos.org e-mail :^) 2023-07-15 16:21:29 +02:00
.pre-commit-config.yaml Meta: Add a post-commit commit message linter hook 2021-05-02 16:28:01 +02:00
.prettierignore LibJS: Add DisposableStack{, Prototype, Constructor} 2023-01-23 09:56:50 +00:00
.prettierrc Meta: Move prettier config files to the root of the repository 2020-08-24 18:21:33 +02:00
.ycm_extra_conf.py Meta: Remove i686 references in YCM configuration 2022-12-28 11:53:41 +01:00
azure-pipelines.yml CI: Test using Clang for ASAN+UBSAN on Linux, add nightly GCC job 2024-04-23 21:16:53 -06:00
CMakeLists.txt Toolchain: Update LLVM to 18.1.3 2024-04-18 13:14:33 -06:00
CONTRIBUTING.md Meta: Switch to clang-format-18 as the standard formatter 2024-04-24 16:50:01 -04:00
flake.lock nix: Clean up files, use good practices 2024-03-25 14:19:34 -06:00
flake.nix nix: Clean up files, use good practices 2024-03-25 14:19:34 -06:00
LICENSE Meta: Update the year range in LICENSE 2024-01-06 17:39:16 -05:00
README.md Meta: Add section about Ladybird to top-level README 2024-04-30 05:59:36 -06:00
SECURITY.md Meta: Add a security policy 2022-06-29 03:29:27 +00:00

README.md

SerenityOS and Ladybird

SerenityOS is a graphical Unix-like operating system for x86-64 computers.

Ladybird is a cross-platform independent web browser built from SerenityOS components.

GitHub Actions Status Azure DevOps Status Fuzzing Status Sonar Cube Static Analysis Discord

FAQ | Documentation | Build Instructions

About SerenityOS

SerenityOS is a love letter to '90s user interfaces with a custom Unix-like core. It flatters with sincerity by stealing beautiful ideas from various other systems.

Roughly speaking, the goal is a marriage between the aesthetic of late-1990s productivity software and the power-user accessibility of late-2000s *nix. This is a system by us, for us, based on the things we like.

You can watch videos of the system being developed on YouTube:

About Ladybird

Ladybird is a cross-platform independent web browser built from SerenityOS components. It is a separate project from SerenityOS, but it uses the SerenityOS build system and shares much of the same code. All the browser UI code lives in the Serenity repository under the Ladybird directory. The SerenityOS LibGUI port of Ladybird lives in the Userland/Applications/Browser directory. All the implementation details are in the Userland/Libraries and Userland/Services directories.

See the Ladybird README.md for more information.

SerenityOS Screenshot

Screenshot as of c03b788.png

SerenityOS Features

  • Modern x86 64-bit kernel with pre-emptive multi-threading
  • Browser with JavaScript, WebAssembly, and more (check the spec compliance for JS, CSS, and Wasm)
  • Security features (hardware protections, limited userland capabilities, W^X memory, pledge & unveil, (K)ASLR, OOM-resistance, web-content isolation, state-of-the-art TLS algorithms, ...)
  • System services (WindowServer, LoginServer, AudioServer, WebServer, RequestServer, CrashServer, ...) and modern IPC
  • Good POSIX compatibility (LibC, Shell, syscalls, signals, pseudoterminals, filesystem notifications, standard Unix utilities, ...)
  • POSIX-like virtual file systems (/proc, /dev, /sys, /tmp, ...) and ext2 file system
  • Network stack and applications with support for IPv4, TCP, UDP; DNS, HTTP, Gemini, IMAP, NTP
  • Profiling, debugging and other development tools (Kernel-supported profiling, CrashReporter, interactive GUI playground, HexEditor, HackStudio IDE for C++ and more)
  • Libraries for everything from cryptography to OpenGL, audio, JavaScript, GUI, playing chess, ...
  • Support for many common and uncommon file formats (PNG, JPEG, GIF, MP3, WAV, FLAC, ZIP, TAR, PDF, QOI, Gemini, ...)
  • Unified style and design philosophy, flexible theming system, custom (bitmap and vector) fonts
  • Games (Solitaire, Minesweeper, 2048, chess, Conway's Game of Life, ...) and demos (CatDog, Starfield, Eyes, mandelbrot set, WidgetGallery, ...)
  • Every-day GUI programs and utilities (Spreadsheet with JavaScript, TextEditor, Terminal, PixelPaint, various multimedia viewers and players, Mail, Assistant, Calculator, ...)

... and all of the above are right in this repository, no extra dependencies, built from-scratch by us :^)

Additionally, there are over three hundred ports of popular open-source software, including games, compilers, Unix tools, multimedia apps and more.

How do I read the documentation?

Man pages are available online at man.serenityos.org. These pages are generated from the Markdown source files in Base/usr/share/man and updated automatically.

When running SerenityOS you can use man for the terminal interface, or help for the GUI.

Code-related documentation can be found in the documentation folder.

How do I build and run this?

See the SerenityOS build instructions or the Ladybird build instructions.

The build system supports a cross-compilation build of SerenityOS from Linux, macOS, Windows (with WSL2) and many other *Nixes. The default build system commands will launch a QEMU instance running the OS with hardware or software virtualization enabled as supported.

Ladybird runs on the same platforms that can be the host for a cross build of SerenityOS and on SerenityOS itself.

Get in touch and participate!

Join our Discord server: SerenityOS Discord

Before opening an issue, please see the issue policy.

A general guide for contributing can be found in CONTRIBUTING.md.

Authors

And many more! See here for a full contributor list. The people listed above have landed more than 100 commits in the project. :^)

License

SerenityOS is licensed under a 2-clause BSD license.