git: 554f43c0a7 - main - docs: Remove references to `make world`
Ed Maste <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.cvs.doc |
|---|---|
| Message-ID | <[email protected]> |
The branch main has been updated by emaste: URL: https://cgit.FreeBSD.org/doc/commit/?id=554f43c0a7afc3e7e6d78611c8bb8fb41f7810e7 commit 554f43c0a7afc3e7e6d78611c8bb8fb41f7810e7 Author: Ed Maste <[email protected]> AuthorDate: 2025-05-23 19:40:50 +0000 Commit: Ed Maste <[email protected]> CommitDate: 2025-05-23 19:46:12 +0000 docs: Remove references to `make world` Two of these seemed to be used in the sense of "building the system." The other one was a literal command, but was incorrect. Reviewed by: jhb Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D50471 --- documentation/content/en/articles/committers-guide/_index.adoc | 2 +- documentation/content/en/books/developers-handbook/policies/_index.adoc | 2 +- documentation/content/en/books/developers-handbook/tools/_index.adoc | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/documentation/content/en/articles/committers-guide/_index.adoc b/documentation/content/en/articles/committers-guide/_index.adoc index 91c14a89c1..f8a617ace1 100644 --- a/documentation/content/en/articles/committers-guide/_index.adoc +++ b/documentation/content/en/articles/committers-guide/_index.adoc @@ -3167,7 +3167,7 @@ There is no shame in asking "how in the heck do I do this?" We already know you . Test your changes before committing them. + If your changes are to the kernel, make sure you can still compile both GENERIC and LINT. -If your changes are anywhere else, make sure you can still make world. +If your changes are anywhere else, make sure you can still compile userspace via `make buildworld`. If your changes are to a branch, make sure your testing occurs with a machine which is running that code. If you have a change which also may break another architecture, be sure and test on all supported architectures. Please ensure your change works for diff --git a/documentation/content/en/books/developers-handbook/policies/_index.adoc b/documentation/content/en/books/developers-handbook/policies/_index.adoc index f4df912da3..a72c1a691b 100644 --- a/documentation/content/en/books/developers-handbook/policies/_index.adoc +++ b/documentation/content/en/books/developers-handbook/policies/_index.adoc @@ -133,7 +133,7 @@ The following policies apply to including encumbered files in the FreeBSD source .. The _Release Engineer_ decides whether or not it goes into the release. . User-land files: -.. The link:https://www.FreeBSD.org/administration/#t-core[Core team] decides if the code should be part of `make world`. +.. The link:https://www.FreeBSD.org/administration/#t-core[Core team] decides if the code should be part of the installed base system. .. The link:https://www.FreeBSD.org/administration/#t-re[Release Engineering] decides if it goes into the release. [[policies-shlib]] diff --git a/documentation/content/en/books/developers-handbook/tools/_index.adoc b/documentation/content/en/books/developers-handbook/tools/_index.adoc index d6ef9ec467..608851ecc7 100644 --- a/documentation/content/en/books/developers-handbook/tools/_index.adoc +++ b/documentation/content/en/books/developers-handbook/tools/_index.adoc @@ -530,7 +530,7 @@ In other words, this is the rule which tells make how to re-compile [.filename]# So, when you type `make`, it will make sure that [.filename]#foo# is up to date with respect to your latest changes to [.filename]#foo.c#. This principle can be extended to [.filename]#Makefile#'s with hundreds of targets-in fact, on FreeBSD, -it is possible to compile the entire operating system just by typing `make world` in the appropriate directory! +it is possible to compile the entire operating system just by typing `make buildworld` at the top level directory in the src tree. Another useful property of makefiles is that the targets do not have to be programs. For instance, we could have a make file that looks like this: