Skip to content
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

/internals/build-system.mdx: Update link for documentation #353

Merged
merged 1 commit into from
Oct 21, 2023
+1 −1
Merged

/internals/build-system.mdx: Update link for documentation #353

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
2 changes: 1 addition & 1 deletion content/docs/internals/build-system.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -251,7 +251,7 @@ config APPHELLOWORLD_DEPENDENCIES

In this example, `LIB1` and `LIB2` would be enabled (the user can't unselect them).
Additionally, if the user did not provide and select any `libc`, the Unikraft internal replacement `nolibc` would be selected.
You can find a documentation of the syntax in the [Linux kernel tree](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/plain/Documentation/kbuild/kconfig-language.txt).
You can find a documentation of the syntax in the [Linux kernel tree](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/plain/Documentation/kbuild/kconfig-language.rst).
Of course, you could also directly define a dependency on a particular `libc` (e.g., `libmusl`), instead.
You can also depend on feature flags (like `HAVE_LIBC`) to provide or hide options.
The feature flag `HAVE_LIBC` in this example is set as soon as a proper and full-fledged `libc` was selected by the user.
Expand Down