SliTaz GNU/Linux official and community documentation wiki.
Translations of this page:

This is an old revision of the document!

You must read the Cookbook first. Its a great collection of documents. This guides supplements the cookbook with some tips that you are likely to face while compiling a package for SliTaz


  1. Add “slitaz-dev-pkgs” package. Its a meta package to add some of the useful *-dev packages
  2. Compilation Errors like
    • checking for $PKG… configure: error: Couldn't find $PKG >= 1.0.0,
    • configure: error: Couldn't find $FILENAME
    • use: “tazpkg search-pkgname $FILENAME” to find the package with the missing file; Add this package to the BUILD_DEPENDS in the receipt.
  3. Read receipts of other packages for standardization. The problems you face may already have a solution in one of the receipts. Some examples receipts include:
    • cups : to strip files other than .so in usr/lib, and to compress some driver files
    • ndiswrapper-driver : to cook linux modules
    • mplayer-svn : to create packages from svn/git
    • 915resolution or busybox : to add patches
    • nvidia : to create non-free packages that need linux package for modules compilation
    • get-* : to create non-free packages
    • *-dev : to see how to create a dev receipt
  4. Create lighter packages. Always remember to disable gnome dependencies or any other dependencies that are not so useful. Always do “configure -h” to see the compile options. Many packages have auto-dependency tracking, i.e., if it finds a correspondign *-dev file it will enable an option. So, if you don't disable an unwanted dependency, then when a package is cooked on SliTaz tank server, it is likely that a package won't run because of a missing dependency. The missing dependency problems that are often reported on the forum is often caused due to this problem.
  5. 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 sometime as you expect upstream package to be properly distributed. firefox-dev is one such example.
  6. gcc4.4 patches : 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-in
  7. Create a chroot environment
en/guides/tazwoktips.1270569819.txt.gz · Last modified: 2010/07/08 17:17 (external edit)