slitaz-doc-wiki-data view pages/en/guides/tazwoktips.txt @ rev 7
Add pages/en folder.
| author | Christopher Rogers <slaxemulator@gmail.com> |
|---|---|
| date | Sat Feb 26 12:17:18 2011 +0000 (2011-02-26) |
| parents | |
| children |
line source
1 ====== Tazwoktips ======
3 You must read the [[http://doc.slitaz.org/en:cookbook:start|Cookbook]] first - it's a great collection of documents. This guide supplements the cookbook with some tips that you are most likely to face while compiling packages for SliTaz.
5 ===== Tips =====
7 - Add the "slitaz-dev-pkgs" package - it's a meta package that adds some of the useful *-dev packages
8 - Compilation Errors like
9 * checking for $PKG... configure: error: Couldn't find $PKG >= 1.0.0,
10 * configure: error: Couldn't find $FILENAME
11 * use: "tazpkg search-pkgname $FILENAME" to find the package with the missing file; Add this package to the BUILD_DEPENDS in the receipt
12 - Read receipts of the other packages for standardization. The problems you face may already have a solution in one of these receipts. Some example receipts include:
13 * xorg-libSM (or any xorg-*) : to use a $SOURCE variable
14 * cups : to strip files other than .so in usr/lib, and to compress some driver files
15 * ndiswrapper-driver or broadcom-wl : to cook linux modules
16 * mplayer-svn : to create packages from a svn/git repository
17 * 915resolution or busybox : to add patches
18 * nvidia : to create non-free packages that need the linux package for compiling modules
19 * get-* : to create non-free packages
20 * *-dev : to see how to create a dev receipt
21 - Create lighter packages. Always remember to disable gnome dependencies or any other dependencies that are not so useful. Always use "configure --help" to see the compile options. Many packages have auto-dependency tracking, i.e., if it finds a corresponding *-dev package installed on the system, it will auto-enable an option. So, if you don't disable an unwanted dependency, then when a package is cooked on the SliTaz tank server, it is likely that the package won't run properly because of the missing dependency. The missing dependency problems that are often reported on the forum are caused due to this problem.
22 - Missing .pc files : Sometimes a dev package created upstream misses .pc files, so pkg-config cannot locate the corresponding dev files correctly. This can play havoc sometimes as you expect the upstream packages to be properly distributed. firefox-dev is one such example.
23 - gcc4.4 patches : The new stricter format of gcc4.4 breaks many packages. This is quite a common problem. You need to either create a simple patch or see if a new upgrade is available upstream. See mplayerplug-svn.
24 - Use a chroot environment and keep it clean so that you can submit the receipt with the correct BUILD_DEPENDS.
26 ----
27 \\
28 ^ Page Review Section ^^
29 |Quality| Good |
30 |Review| Minor Updates |
31 |Priority| Medium |
32 |Problems| add a [[http://forum.slitaz.org|forum post link]]|
33 |::: | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
34 |How to Improve| Suggest briefly|
35 |::: | |
37 \\
38 ----