Skip to content

Commit 884673b

Browse files
committed
Update content
1 parent ad1e5d6 commit 884673b

2 files changed

Lines changed: 3 additions & 21 deletions

File tree

content/docs/getting-started/building.md

Lines changed: 2 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -71,8 +71,6 @@ git clone https://github.com/VitruvianOS/Vitruvian.git
7171

7272
## Building VitruvianOS
7373

74-
After cloning, enter the source directory and run:
75-
7674
```bash
7775
git submodule update --init --recursive
7876
mkdir buildtools/ && mkdir generated.x86/
@@ -84,9 +82,9 @@ cd ../generated.x86 && ../build/scripts/setupenv.sh
8482
ninja
8583
```
8684

87-
`setupenv.sh` uses `debootstrap` to bootstrap a minimal Debian Trixie (amd64) environment under `generated.x86/image_tree/chroot`. It installs both the base live-boot packages and all required `-dev` packages inside the chroot, and writes `imagekernelversion.conf` with the chroot's kernel version. This chroot is also the live image that gets packed into the ISO/raw image later.
85+
`setupenv.sh` uses `debootstrap` to bootstrap a minimal Debian Trixie (amd64) environment under `generated.x86/image_tree/chroot`, installs all required `-dev` packages inside it, and writes `imagekernelversion.conf` with the chroot kernel version. The compiler and build tools are always taken from the host.
8886

89-
`--chroot-build` tells `configure` to resolve all headers and libraries from the chroot instead of the host, keeping the build fully isolated. The compiler and build tools are always taken from the host.
87+
If you only need to build and run Vitruvian locally without producing an image, you can skip `setupenv.sh` and run `../configure` without `--chroot-build`, building directly against the host libraries instead.
9088

9189
### configure options
9290

@@ -118,22 +116,6 @@ x86_64 is selected by default. To make the selection explicit:
118116
../configure --arch=x86_64
119117
```
120118

121-
### Development build (without image)
122-
123-
If you only need to build and run Vitruvian locally without creating a bootable image, you can skip `setupenv.sh` and configure directly against the host libraries:
124-
125-
```bash
126-
../configure
127-
ninja
128-
```
129-
130-
This requires the relevant `-dev` packages installed on the host.
131-
132-
To use a chroot at a custom path:
133-
134-
```bash
135-
../configure --chroot-build --chroot-path=/path/to/chroot
136-
```
137119

138120
## Building the .deb Package
139121

content/docs/getting-started/faq.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ The core kits (Application, Interface, Storage, Support) are functional enough t
4444

4545
## Is there a package manager?
4646

47-
YesVitruvian ships as a Debian-derived image, so **apt** is available for installing packages from Debian repositories alongside native Vitruvian software.
47+
Yes. Vitruvian ships as a Debian-derived image, so **apt** is the package manager. The plan is to give users access to the full Debian software archive — over 120,000 packages — directly from Vitruvian, alongside native Vitruvian software. If it runs on Debian, it should be installable on Vitruvian.
4848

4949
---
5050

0 commit comments

Comments
 (0)