Readme.Compiling.md: Use new build profiles

When #15963 was fixed, some build profiles were succeeded by newer
ones, while the older ones were completely removed. However, this
document was never updated to specifically reflect this change.

Additionally, some headers were slightly improved to make them more
descriptive.

Change-Id: If89e927bef3b87df4e54eecb13a69d877b90e6af
Reviewed-on: https://review.haiku-os.org/c/haiku/+/6001
Tested-by: Commit checker robot <no-reply+buildbot@haiku-os.org>
Reviewed-by: Adrien Destugues <pulkomandy@pulkomandy.tk>
This commit is contained in:
Panagiotis "Ivory" Vasilopoulos 2023-01-15 12:17:05 +01:00 committed by Adrien Destugues
parent 75070a4089
commit 979de7d73d

View File

@ -175,18 +175,27 @@ There are various ways in which you can run `jam`:
Be sure to read `build/jam/UserBuildConfig.ReadMe` and `UserBuildConfig.sample`,
as they contain information on customizing your build of Haiku.
### Building a Haiku anyboot file
### Building a Haiku anyboot image (Nightly)
```
jam -q @anyboot-image
jam -q @nightly-anyboot
```
This generates an image file named `haiku-anyboot.image` in your output
This generates an image file named `haiku-nightly-anyboot.iso` in your output
directory under `generated/`.
### Building a Haiku raw image (Nightly)
```
jam -q @nightly-raw
```
This generates an image file named `haiku.image` in your output directory under
`generated/`.
### Building a VMware image file
```
jam -q @vmware-image
jam -q @nightly-vmware
```
This generates an image file named `haiku.vmdk` in your output
directory under `generated/`.