diff options
| -rw-r--r-- | doc/pkg/basic-expat.mdwn | 26 |
1 files changed, 15 insertions, 11 deletions
diff --git a/doc/pkg/basic-expat.mdwn b/doc/pkg/basic-expat.mdwn index a71c3fb..8fda25e 100644 --- a/doc/pkg/basic-expat.mdwn +++ b/doc/pkg/basic-expat.mdwn @@ -162,13 +162,17 @@ The `build` makefile must be executable, so set its file mode: We can now make **opkbuild** prepare our build work area. - $ opkbuild -b -c -T nop + $ sudo prokit build $root -b -c -T nop . -The options are explained in the help output of opkbuild, obtained by running -`opkbuild -h`. The `-b` option tells **opkbuild** to build only binary -packages (no source package). The `-c` option tells it to not clean up the work -area after building packages. The `-T` option specifies a target to be built -instead of the standard `build` and `install` targets. +We're running **opkbuild** through +[[**prokit-build**(1)|dev/prokit/prokit-build.1]]. `$root` is the root +directory of our ProteanOS development system. + +The options are explained in the help output of **opkbuild**, obtained by +running `prokit build $root -h .`. The `-b` option tells **opkbuild** to build +only binary packages (no source package). The `-c` option tells it to not clean +up the work area after building packages. The `-T` option specifies a target to +be built instead of the standard `build` and `install` targets. Now look in `tmp/src/`, the location of the source code within the build work area. @@ -213,7 +217,7 @@ The `touch $@` command is recommended by SPF 2.0: We can now build Expat. - $ opkbuild -b -c -T build + $ sudo prokit build $root -b -c -T build . [spf-build]: http://specs.proteanos.com/spf-2.0/buildsys.html#build [no-op]: https://en.wiktionary.org/wiki/no-op @@ -256,7 +260,7 @@ about what it does. Install Expat: - $ opkbuild -b -c -T install + $ sudo prokit build $root -b -c -T install . Splitting Files Into Binary Packages ------------------------------------ @@ -447,7 +451,7 @@ With these pathname patterns done, we can add **oh-installfiles**(1) to our Now run **opkbuild** again: - $ opkbuild -b -c -T install + $ sudo prokit build $root -b -c -T install . You can verify that all files were installed where they should be: @@ -720,12 +724,12 @@ the metadata in our packaging since the first time we ran **opkbuild**, this cache file is out-of-date. Also, we should make sure that the entire build process still works. So let's clean up the work area before going any further. - $ rm -Rf tmp/ + $ sudo rm -Rf tmp/ Now let's run **opkbuild** again, this time completely building all of our source and binary packages and cleaning up automatically when we're done. - $ opkbuild + $ sudo prokit build $root . After that finishes, you should see the built packages in the parent directory. |