Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
en:cookbook:wok [2012/04/06 14:12] linea |
en:cookbook:wok [2017/04/17 18:31] hgt create package after writing recipe |
||
---|---|---|---|
Line 39: | Line 39: | ||
</code> | </code> | ||
- | More information on the use of the Mercurial VCS is available from its [[http://mercurial.selenic.com/|website]] and the "[[http://hgbook.red-bean.com/|Hg Book]]". | + | More information on the use of the Mercurial VCS is available from its [[http://mercurial-scm.org/|website]] and the "[[http://hgbook.red-bean.com/|Hg Book]]". |
=== Cloning the Wok === | === Cloning the Wok === | ||
Line 76: | Line 76: | ||
When Cookutils has finished building M4, its package is placed in the directory specified by the configuration file (///home/slitaz///packages by default). If all went well, you can install the package on the host system or use it to generate a LiveCD distribution via Tazlito! | When Cookutils has finished building M4, its package is placed in the directory specified by the configuration file (///home/slitaz///packages by default). If all went well, you can install the package on the host system or use it to generate a LiveCD distribution via Tazlito! | ||
- | When you are familiar with [[en:cookbook:receipt|receipts]] and the compilation process, you can use the following command to create a new package interactively before writing its receipt: | + | When you are familiar with [[en:cookbook:receipt|receipts]] and the compilation process, you can use the following command to create a new package, after interactively writing its receipt: |
<code> # cook new <packageName> --interactive </code> | <code> # cook new <packageName> --interactive </code> | ||
Line 102: | Line 102: | ||
The official SliTaz packages are optimized for **i486**, the optimization arguments used to configure are specified in **/etc/slitaz/cook.conf** and can be called via the variable $CONFIGURE_ARGS. If you want to compile a package with different arguments, you can modify the Cookutils configuration file: | The official SliTaz packages are optimized for **i486**, the optimization arguments used to configure are specified in **/etc/slitaz/cook.conf** and can be called via the variable $CONFIGURE_ARGS. If you want to compile a package with different arguments, you can modify the Cookutils configuration file: | ||
- | <file> | + | <file bash> |
CONFIGURE_ARGS="--build=i486-pc-linux-gnu --host=i486-pc-linux-gnu" | CONFIGURE_ARGS="--build=i486-pc-linux-gnu --host=i486-pc-linux-gnu" | ||
</file> | </file> |