From patchwork Sun Nov 11 13:14:45 2012 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Samuel Martin X-Patchwork-Id: 198265 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Received: from silver.osuosl.org (silver.osuosl.org [140.211.166.136]) by ozlabs.org (Postfix) with ESMTP id 4E2352C0040 for ; Mon, 12 Nov 2012 00:16:10 +1100 (EST) Received: from localhost (localhost [127.0.0.1]) by silver.osuosl.org (Postfix) with ESMTP id DC8622548D; Sun, 11 Nov 2012 13:16:08 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from silver.osuosl.org ([127.0.0.1]) by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zCFdd0QDzEcD; Sun, 11 Nov 2012 13:16:01 +0000 (UTC) Received: from ash.osuosl.org (ash.osuosl.org [140.211.166.34]) by silver.osuosl.org (Postfix) with ESMTP id C178430CED; Sun, 11 Nov 2012 13:15:55 +0000 (UTC) X-Original-To: buildroot@lists.busybox.net Delivered-To: buildroot@osuosl.org Received: from whitealder.osuosl.org (whitealder.osuosl.org [140.211.166.138]) by ash.osuosl.org (Postfix) with ESMTP id DB7018F753 for ; Sun, 11 Nov 2012 13:15:35 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by whitealder.osuosl.org (Postfix) with ESMTP id B132A8C2D7 for ; Sun, 11 Nov 2012 13:15:31 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from whitealder.osuosl.org ([127.0.0.1]) by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iV0jfrVyqWTu for ; Sun, 11 Nov 2012 13:15:30 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-we0-f171.google.com (mail-we0-f171.google.com [74.125.82.171]) by whitealder.osuosl.org (Postfix) with ESMTPS id 6C8E78C2A6 for ; Sun, 11 Nov 2012 13:15:30 +0000 (UTC) Received: by mail-we0-f171.google.com with SMTP id s43so3028443wey.16 for ; Sun, 11 Nov 2012 05:15:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:x-mailer:in-reply-to:references; bh=vKqTGTo6NBtBK5DI69awGReLv8D9pfjul5efHMG9j6M=; b=MEBTDRxuNPXrpf1gu6TvI4TM8F2ha3Sl1a5MIwWkn8DueEyVhoirHJDkXFbD/W4SZg bDJ16HpLHKJCt7dmmQmZDqZV+YJCTZebnqjIy/ivWEZ2q/xz9Q40XWeVe6sLOQ1V0oY5 Uqcse2lqYl4Suq19rbhSSuLbgtzAWm/QucL/dhe+6d+stKs1+6jIXnY63El5oleaGJVx euZKVNuK2NZkLdoEhHX2W9qlwU7+2Z9Ok+Azlr6WeXZh8lizS5/Y/q7Boiulceg5OQny NS48KcJo7d9pz0a1yr/jhHvwsTDydihrcIkPMgbHzbXAITndtAhtiPKJhLy58qSVaCuI Z3hQ== Received: by 10.216.214.101 with SMTP id b79mr7158363wep.1.1352639730160; Sun, 11 Nov 2012 05:15:30 -0800 (PST) Received: from localhost.localdomain (ivr94-4-82-229-165-48.fbx.proxad.net. [82.229.165.48]) by mx.google.com with ESMTPS id hv4sm10262550wib.0.2012.11.11.05.15.28 (version=SSLv3 cipher=OTHER); Sun, 11 Nov 2012 05:15:29 -0800 (PST) From: Samuel Martin To: buildroot@busybox.net Date: Sun, 11 Nov 2012 14:14:45 +0100 Message-Id: <1352639701-27829-8-git-send-email-s.martin49@gmail.com> X-Mailer: git-send-email 1.8.0 In-Reply-To: <1352639701-27829-1-git-send-email-s.martin49@gmail.com> References: <1352639701-27829-1-git-send-email-s.martin49@gmail.com> Subject: [Buildroot] [PATCH 07/23] manual: customize-rootfs.txt: refactoring, misc. fixes and update X-BeenThere: buildroot@busybox.net X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion and development of buildroot List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Errors-To: buildroot-bounces@busybox.net Sender: buildroot-bounces@busybox.net Signed-off-by: Samuel Martin diff --git a/docs/manual/customize-rootfs.txt b/docs/manual/customize-rootfs.txt index 7ac5195..d6224ff 100644 --- a/docs/manual/customize-rootfs.txt +++ b/docs/manual/customize-rootfs.txt @@ -4,7 +4,8 @@ Customizing the generated target filesystem ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -There are a few ways to customize the resulting target filesystem: +Besides changing one or another configuration through +make *config+, +there are a few ways to customize the resulting target filesystem: * Customize the target filesystem directly and rebuild the image. The target filesystem is available under +output/target/+. You can @@ -12,28 +13,33 @@ There are a few ways to customize the resulting target filesystem: rebuild the target filesystem image. This method allows you to do anything to the target filesystem, but if you decide to completely rebuild your toolchain and tools, these changes will be lost. + _Changes are not resistent to the +make clean+ command_. * Create your own 'target skeleton'. You can start with the default skeleton available under +system/skeleton+ and then customize it to suit your needs. The +BR2_ROOTFS_SKELETON_CUSTOM+ and +BR2_ROOTFS_SKELETON_CUSTOM_PATH+ will allow you to specify the - location of your custom skeleton. At build time, the contents of the + location of your custom skeleton. These options can be found in the + +System configuration+ menu. At build time, the contents of the skeleton are copied to output/target before any package installation. * In the Buildroot configuration, you can specify the path to a - post-build script, that gets called 'after' Buildroot builds all the + *post-build script*, that gets called 'after' Buildroot builds all the selected software, but 'before' the rootfs packages are - assembled. The destination root filesystem folder is given as the - first argument to this script, and this script can then be used to - copy programs, static data or any other needed file to your target - filesystem. You should, however, use this feature with care. - Whenever you find that a certain package generates wrong or unneeded - files, you should fix that package rather than work around it with a - post-build cleanup script. + assembled. The +BR2_ROOTFS_POST_BUILD_SCRIPT+ will allow you to + specify the location of your post-build script. This option can be + found in the +System configuration+ menu. The destination root + filesystem folder *is given as the first argument to this script, + and this script can then be used to copy programs, static data or + any other needed file to your target filesystem. You should, + however, use this feature with care. Whenever you find that a + certain package generates wrong or unneeded files, you should fix + that package rather than work around it with a post-build cleanup + script. _Among these first 3 methods, this one should be prefere_d. * A special package, 'customize', stored in +package/customize+ can be used. You can put all the files that you want to see in the final target root filesystem in +package/customize/source+, and then - enable this special package in the configuration system. - + enable this special package in the configuration system. _This + method is marked as deprecated_.