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

Jump to bottom

updating readme to reflect new klib location #2077

Merged
merged 2 commits into from
Nov 12, 2024
Merged

updating readme to reflect new klib location #2077

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d093085
updating readme to reflect new klib location
eyberg Nov 11, 2024
993ba8d
.
eyberg Nov 12, 2024
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
13 changes: 9 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -212,12 +212,17 @@ make TARGET=mynewtarget run

You may also wish to use [ops](https://github.com/nanovms/ops) to
develop locally. If that's the case a commonly used idiom is to simply
copy the 3 required files to an appropriate release:
copy the 2 required files to an appropriate release:

```
cp output/tools/bin/mkfs ~/.ops/0.1.47/.
cp output/platform/pc/boot/boot.img ~/.ops/0.1.47/.
cp output/platform/pc/bin/kernel.img ~/.ops/0.1.47/.
cp output/platform/pc/boot/boot.img ~/.ops/0.1.52/.
cp output/platform/pc/bin/kernel.img ~/.ops/0.1.52/.
```

You may also copy the klibs over if you wish to use any of those:

```
cp output/platform/pc/bin/!(test|*.dbg|kernel.*) ~/.ops/0.1.52/.
eyberg marked this conversation as resolved.
Show resolved Hide resolved
```

### Contributing
Expand Down